Skip to content

feat(spans-buffer): Split SUNIONSTORE timing and use stage tags for metrics#108468

Merged
untitaker merged 1 commit intomasterfrom
span-buffer-metrics-improvements
Feb 19, 2026
Merged

feat(spans-buffer): Split SUNIONSTORE timing and use stage tags for metrics#108468
untitaker merged 1 commit intomasterfrom
span-buffer-metrics-improvements

Conversation

@untitaker
Copy link
Copy Markdown
Member

@untitaker untitaker commented Feb 18, 2026

  • split up sunionstore stage into many stages, not sure if we can 100% conclude it's SUNIONSTORE every time otherwise?
  • it's easier to have one metric with a tag for the stage instead of many metrics. the dashboard widget will need less maintenance
  • add a metric for by how many elements a set grew, because we cannot actually get that from the two before/after metrics directly.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 18, 2026
@untitaker untitaker marked this pull request as ready for review February 18, 2026 18:41
@untitaker untitaker requested review from a team as code owners February 18, 2026 18:41
metrics.timing(f"spans.buffer.process_spans.max_{metric}", max_value)
tags = {"stage": metric}
metrics.timing(
"spans.buffer.process_spans.avg_step_latency_ms", sum_value / count, tags=tags
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that this will break all the existing dashboards. Not a deal breaker though.

@untitaker untitaker merged commit 95d718b into master Feb 19, 2026
84 checks passed
@untitaker untitaker deleted the span-buffer-metrics-improvements branch February 19, 2026 15:47
JonasBa pushed a commit that referenced this pull request Feb 19, 2026
…etrics (#108468)

* split up sunionstore stage into many stages, not sure if we can 100%
conclude it's SUNIONSTORE every time otherwise?
* it's easier to have one metric with a tag for the stage instead of
many metrics. the dashboard widget will need less maintenance
* add a metric for by how many elements a set grew, because we cannot
actually get that from the two before/after metrics directly.
mchen-sentry pushed a commit that referenced this pull request Feb 24, 2026
…etrics (#108468)

* split up sunionstore stage into many stages, not sure if we can 100%
conclude it's SUNIONSTORE every time otherwise?
* it's easier to have one metric with a tag for the stage instead of
many metrics. the dashboard widget will need less maintenance
* add a metric for by how many elements a set grew, because we cannot
actually get that from the two before/after metrics directly.
@github-actions github-actions bot locked and limited conversation to collaborators Mar 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

claude-code-assisted Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants