logfire_slo: seed the generated burn-rate alerts' channels at creation#46
Merged
Conversation
…d burn-rate alerts
bruno-espino
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds optional
page_channel_ids/ticket_channel_idsset attributes tologfire_slo, passed to the SLO create API to seed the generated burn-rate alerts' notification channels (page-severity tiers and the ticket tier respectively). Delivery is alert-owned after creation, so the attributes are create-time seeds: the API never returns them, the provider preserves the configured values in state, and changing them later does not modify an existing SLO's alerts (documented on the attributes).