Skip to content

grafana: change default exec err state to Error to match Grafana default#2149

Open
guerremdq wants to merge 1 commit into
mainfrom
grafana-alert-errstate
Open

grafana: change default exec err state to Error to match Grafana default#2149
guerremdq wants to merge 1 commit into
mainfrom
grafana-alert-errstate

Conversation

@guerremdq

Copy link
Copy Markdown

change default exec err state to Error to match Grafana default

Copilot AI review requested due to automatic review settings June 12, 2026 11:05
@guerremdq guerremdq requested a review from a team as a code owner June 12, 2026 11:05
@github-actions

Copy link
Copy Markdown

👋 guerremdq, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@github-actions

github-actions Bot commented Jun 12, 2026

Copy link
Copy Markdown

📊 API Diff Results

No changes detected for module github.com/smartcontractkit/chainlink-common/observability-lib

View full report

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the Grafana alert rule builder defaults in observability-lib so that the exec error state aligns with Grafana’s own default behavior.

Changes:

  • Change the default RuleExecErrState from Alerting to Error when not explicitly set in AlertOptions.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 212 to 214
if options.RuleExecErrState == "" {
options.RuleExecErrState = alerting.RuleExecErrStateAlerting
options.RuleExecErrState = alerting.RuleExecErrStateError
}
@guerremdq guerremdq force-pushed the grafana-alert-errstate branch from 75eefed to 3cb871c Compare June 12, 2026 11:13
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