Skip to content

tempo: add new alerts and runbooks#6276

Merged
javiermolinar merged 8 commits intomainfrom
tempo-add-new-alerts
Feb 2, 2026
Merged

tempo: add new alerts and runbooks#6276
javiermolinar merged 8 commits intomainfrom
tempo-add-new-alerts

Conversation

@javiermolinar
Copy link
Copy Markdown
Contributor

@javiermolinar javiermolinar commented Jan 22, 2026

What this PR does:

It introduces new alerts and runbook entries to make tempo operators life easier:

  • TempoBlockBuildersPartitionsMismatch
  • TempoLiveStoresPartitionsUnowned
  • TempoLiveStoreZoneSeverelyDegraded
  • TempoDistributorUsageTrackerErrors
  • TempoMetricsGeneratorProcessorUpdatesFailing
  • TempoMetricsGeneratorServiceGraphsDroppingSpans
  • TempoMetricsGeneratorCollectionsFailing

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3c8262646c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread operations/tempo-mixin/alerts.libsonnet Outdated
@javiermolinar javiermolinar enabled auto-merge (squash) January 22, 2026 11:52
Comment thread operations/tempo-mixin-compiled/alerts.yaml
Comment thread operations/tempo-mixin/runbook.md Outdated
@javiermolinar
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a9236849ab

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +344 to +347
- "alert": "TempoMetricsGeneratorProcessorUpdatesFailing"
"annotations":
"message": "Metrics-generator processor updates are failing for tenant {{ $labels.tenant }} in {{ $labels.cluster }}/{{ $labels.namespace }}."
"runbook_url": "https://github.com/grafana/tempo/tree/main/operations/tempo-mixin/runbook.md#TempoMetricsGeneratorProcessorUpdatesFailing"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Complete the compiled alert definition

The compiled alerts.yaml now terminates immediately after the annotations for TempoMetricsGeneratorProcessorUpdatesFailing, so this alert (and anything that should follow) is missing the required expr/for/labels fields. Prometheus rule files require an expr for each alert; loading this compiled mixin will fail validation or silently drop the alert group depending on the loader, so users consuming operations/tempo-mixin-compiled/alerts.yaml will not be able to load the rules. Regenerating the compiled file or fixing the truncation resolves this.

Useful? React with 👍 / 👎.

@javiermolinar javiermolinar merged commit 5eb4cab into main Feb 2, 2026
23 checks passed
@javiermolinar javiermolinar deleted the tempo-add-new-alerts branch February 2, 2026 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants