getsentry / getsentry/sentry

Monitor by segment

Open
#111,876 4 comments 0 reactions 0 assignees View on GitHub
Feature Product Area: Alerts Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

I liked this Sentry blog post ([Green dashboards, red flags](https://blog.sentry.io/green-dashboards-red-flags/)), in particular this part

> Monitor them by segment. Not averages. By customer tier, by region, by device, by release. The bug that breaks your biggest customer doesn't show up in aggregate metrics.

However, I'm not sure how to achieve this at scale without manual effort creating new alerts for each of the segments. I would like to be able to be alerted if, for example, API route latency for a segment I define (e.g., tenant id) was elevated, rather than API route latency in aggregate. In theory, I could create new alerts for each tenant, but this is very tedious.

### Solution Brainstorm

Let users define a segment / group by field for an alert, then do separate alerting for each segment.

### Product Area

Alerts

Contributor guide

Open the contributing guide

Research direction

Start with the Alerts product area and read the linked Sentry blog post for the motivating example. Identify how users could define a segment or group-by field and what separate alerting per segment should mean; the issue is done when the behavior and scope are specified well enough to implement and validate.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.