Group history

An error group's page shows how the group behaves over time, so you can see a pattern without reading its occurrences one by one.

What the section showsCopy Anchor Link

• Occurrences. One bar per hour over 7 days, per 6 hours over 30 days and per day over 90 days.
• Tickets. A diamond for each ticket of the group, by severity. Select one to open it.
• Releases. A mark where the group was first seen on each release. Send release with your logs to fill this row.
• When it happens. A weekday by hour heatmap, with the busiest hour stated as a share of the occurrences.

The history shows counts only. It never interprets them.

Range and planCopy Anchor Link

The range follows the plan's retention: 7 days on Free, 30 on Pro and 90 on Team. A range above the plan shows a lock and leads to the plans. The API answers 403 plan-limit-reached.

EnvironmentsCopy Anchor Link

Occurrences are counted per environment. When a group has occurred in more than one, a selector lets you read one of them; tickets and releases stay the group's. See GET /v1/groups/{group_id}/history.

Time zoneCopy Anchor Link

Longer buckets and the heatmap follow the project's time zone, set in its notification settings. A daylight-saving change makes one bucket shorter or longer.

Counted from hereCopy Anchor Link

Occurrences are counted per hour since this feature exists, and kept for your plan's retention. On an older group, a dashed marker shows the oldest hour counted: time before it was not counted, which does not mean the group did not occur. Earlier occurrences are in the group's total but not in the chart.