Skip to content

Commit 1e99cc6

Browse files
imatwawanaPeloWriterleedongwei
authored
add updated org stats content for EA (#3419)
* add updated org stats content * Update src/docs/product/accounts/quotas/org-stats/index.mdx Add link and wording edit Co-authored-by: Fiona <[email protected]> * Update src/docs/product/accounts/quotas/org-stats/index.mdx Style edits Co-authored-by: Fiona <[email protected]> * Update src/docs/product/accounts/quotas/org-stats/index.mdx Wording edits Co-authored-by: Fiona <[email protected]> * Apply suggestions from code review Edited to move definitions of accepted, filtered, dropped into intro * remove EA notes update language * Update src/docs/product/accounts/quotas/manage-event-stream-guide.mdx * Apply suggestions from code review Adding time zone information; changing "time period" to "date range" * feat(screenshot) * ref: Rename rate-limit to dropped * Update src/docs/product/accounts/quotas/org-stats/index.mdx Co-authored-by: Danny Lee <[email protected]> * Apply suggestions from code review Co-authored-by: Danny Lee <[email protected]> Co-authored-by: Fiona <[email protected]> Co-authored-by: Danny Lee <[email protected]>
1 parent 7ea93f3 commit 1e99cc6

File tree

3 files changed

+45
-8
lines changed

3 files changed

+45
-8
lines changed

src/docs/product/accounts/quotas/manage-event-stream-guide.mdx

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Manage Your Event Stream, a Guide
3-
sidebar_order: 3
3+
sidebar_order: 10
44
redirect_from:
55
- /guides/manage-event-stream/
66
description: "Helps you use the tools Sentry provides to control the _type_ and _amount_ of errors that are monitored."
@@ -131,17 +131,17 @@ A good way to set a project rate limit is by figuring out the expected event vol
131131

132132
### > **How can I see a breakdown of incoming events?**
133133

134-
The `Stats` view displays details about the total number of events Sentry has received across your entire organization over the last week. The report breaks down the events by project into three categories:
134+
**Org Stats** displays details about the total number of events Sentry has received across your entire organization for up to 90 days. The report breaks down the events by project into three categories:
135135

136-
- **Accepted**: events processed and persisted displayed in your event stream.
137-
- **Rate Limited**: events that were dropped due to the limit being hit.
138-
- **Filtered**: events that were blocked based on your inbound filter rules.
136+
- **Accepted**: Events processed and displayed in your event stream.
137+
- **Dropped**: Events that were discarded due to a limit being hit.
138+
- **Filtered**: Events that were blocked based on your inbound filter rules.
139139

140-
![STATS View](manage-event-stream-12.png)
140+
![Overview of Organization Stats page](org-stats/org-stats-page.png)
141141

142-
Clicking on a project name will open the project settings view where you can manage the project's Inbound Filters and Rate Limits.
142+
Clicking on the settings icon next to the project name will open the project's settings page where you can manage its Inbound Filters and Rate Limits.
143143

144-
You can also download monthly reports with a similar break down of all your previous billing periods under `Settings > Usage & Payments > Usage History`
144+
You can also download monthly reports with a similar breakdown of all your previous billing periods under **Settings > Subscription** in the "Usage History" tab.
145145

146146
### > **What are my busiest projects?**
147147

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: "Org Stats"
3+
sidebar_order: 20
4+
description: "Learn about how events are being used across your organization."
5+
---
6+
7+
The **Organization Stats** page allows you to check your organization's event usage while also providing a high-level overview of how different projects are using Sentry. The page reflects events the system has received across your entire organization along with a list of all projects and their consumption of errors, transactions, and attachments. Events fall into one of three categories: _Accepted_, _Filtered_, or _Dropped_. Filtered events are events that were blocked due to your [inbound data filter](/product/data-management-settings/filtering/) rules. Dropped events are ones the system dropped or discarded due to rate limits, quotas, spike protection, or because of invalid data.
8+
9+
You can see which projects have had a recent spike or are the most active and may need more attention. On this page, you can also control the date range that’s displayed, allowing you to focus on a smaller period of time or zoom out for a longer view. The page is designed for org admins, but is available to all team members. This is helpful if a team member who isn't an admin is tasked with reviewing these statistics. Also, this allows team members associated with specific projects to use this page to investigate why their events are being dropped.
10+
11+
![Overview of Organization Stats page](org-stats-page.png)
12+
13+
With the dropdowns at the top of the page, you can set whether the page displays stats for errors, transactions, or attachments, as well as the date range. With the date selector, the time period can be set from an hour to a maximum of 90 days, and all of the page elements change dynamically when you update this setting.
14+
15+
<Note>
16+
17+
This page does not include data about sessions because they are not a billable event type.
18+
19+
</Note>
20+
21+
## Usage Cards
22+
23+
The cards on the page provide high-level usage stats about events, including the total number of events for the period, as well as which ones were accepted, filtered, or dropped.
24+
25+
## Summary Chart
26+
27+
The chart on this page displays a breakdown of events over the selected date range. Depending on the date range that you set the chart to display, each bar in the chart represents a different amount of time or interval. For example, if you set the chart to display seven days, each bar in the chart represents one hour, but if you set it to display 90 days, each bar represents one day. You can also use the “Type” dropdown to set whether the chart shows a cumulative count of events or a daily (or hourly) count.
28+
29+
When you set a date range that results in intervals of one day or more, the time zone is displayed in UTC to ensure consistency for users across different time zones. For time periods with intervals of less than 24 hours, the time zone is based on your "Timezone" setting in **User Settings > Account Details**.
30+
31+
## Project Usage Stats Table
32+
33+
The “Project Usage Stats” table provides insight into per-project usage of your errors, transactions, and attachments over time. The table shows you the total errors, transactions, or attachments. Those events are further broken down into the accepted, filtered, and dropped categories.
34+
35+
Each project in the table has individual settings, which you can access from by clicking the settings icon (gear wheel) next to the name of the project. For instance, you might want to go to the project settings so you can limit the quota consumed by its DSNs. Clicking the name of the project takes you to the **Project Details** page.
36+
37+
The table displays only the projects of the teams that you belong to, unless you have permissions to see all projects.
Loading

0 commit comments

Comments
 (0)