The "Usage Stats" tab shows your organization’s event usage, while also providing a high-level overview of how different projects are using Sentry. The "Team Stats" tab, on the other hand, gives you insights into how your team is using Sentry — for example, it shows you how many issues your team has reviewed and the number of releases they’ve shipped — as well as giving you an overview of the health of your projects.
The "Usage Stats" tab shows you the events Sentry 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 rules. Dropped events are ones the system dropped or discarded due to rate limits, quotas, spike protection, or because of invalid data.
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.
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.
This page does not include data about sessions because they are not a billable event type.
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.
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.
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.
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.
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.
The table displays only the projects of the teams that you belong to, unless you have permissions to see all projects.
This feature is available only if your organization is on a Business plan.
In the "Team Stats" tab you can review information about the overall health of your projects and see how your team is using Sentry. At the top of this page, you can select a team, which will filter the metrics shown below. The default time range for team stats is the last eight weeks, which allows you to compare changes week by week. The team stats are divided into two sections: Project Health and Team Activity.
The "Project Health" section of your team stats provides an overview of your application and shows you a summary of your projects’ Crash Free Rate, as well the User Misery of your team’s key transactions. This gives you a quick idea of which projects and key transactions might need attention from your team. In this section, you can also view how many alerts have been triggered from the metric alerts your team owns.
The "Team Activity" section of your team stats shows how many issues have been reviewed, including a breakdown per project. It also reveals the mean time it took to resolve issues, as well as the number of releases that have been created in the projects that your team owns.