Set PCS staging alert noDataState to OK (fixes perpetual firing)#6581
Merged
Conversation
The staging PCS environment does not process work items, so the WorkItemExecuted telemetry is always empty. With noDataState set to Alerting, this causes the alert to fire indefinitely (since March 13). Changing to OK for staging only — production keeps Alerting so we are still notified if prod telemetry stops. Fixes #10774 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
davfost
approved these changes
May 22, 2026
premun
approved these changes
May 25, 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
3 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.
Problem
The PCS Background Worker Stopped alert has been firing in staging since March 13 (~10 weeks). The staging PCS environment does not process work items, so \WorkItemExecuted\ telemetry is always empty. With
oDataState: Alerting, the alert fires indefinitely.
Premek's team silenced it manually, but rollouts reverted the silence since it was stored in Grafana's runtime state, not in the provisioned config.
Fix
Change
oDataState\ from \Alerting\ to \OK\ in the Staging alert rule file only.
This persists across rollouts because it's in the source-of-truth config file.
Related