getsentry / getsentry/sentry

Support extended percentiles for application metrics

Open
#124,344 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Metrics
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Application Metrics distribution queries currently expose only P50, P75, P90, P95, and P99 in dashboards and the query backend. This prevents dashboards from representing tail values such as P99.9 and P99.99, and editing a widget payload directly does not provide a workaround.

  • The supported aggregations are documented in Application Metrics.
  • The backend defines fixed percentile functions through P99 and does not define a custom percentile() function for Application Metrics (source).
  • max is available but is not equivalent to an extended percentile.

via Michael Chai.

--

View Junior Session [Sentry]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with src/sentry/search/eap/trace_metrics/aggregates.py, especially the fixed percentile functions linked in the issue, then compare them with the documented Application Metrics distribution aggregations. Done means Application Metrics queries and dashboard widgets can represent extended percentiles such as P99.9 and P99.99, with the supported aggregations documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.