[ci] Add Datadog monitor definitions for unattended workflows - #98557
Draft
eps1lon wants to merge 1 commit into
Draft
[ci] Add Datadog monitor definitions for unattended workflows#98557eps1lon wants to merge 1 commit into
eps1lon wants to merge 1 commit into
Conversation
Contributor
Tests PassedCommit: 077c11b |
eps1lon
force-pushed
the
sebbie/ci-workflow-health-monitors
branch
from
September 11, 2026 12:09
56b5ff1 to
80f034b
Compare
eps1lon
force-pushed
the
sebbie/ci-workflow-health-monitors
branch
5 times, most recently
from
September 11, 2026 14:57
8b51580 to
b35d43c
Compare
eps1lon
force-pushed
the
sebbie/ci-workflow-health-monitors
branch
6 times, most recently
from
September 11, 2026 18:04
28bdb20 to
0a56500
Compare
This change adds two import-ready Datadog monitor definitions under `scripts/datadog/workflow-health/` covering the 16 workflows that run without intentional user input, meaning the scheduled workflows and the ones driven purely by `workflow_run`, `issues`, or `issue_comment` events. The failure monitor is a multi-alert `ci-pipelines alert` that notifies on the very first failed run of each workflow and links the specific failed execution through the `ci.pipeline.url` attribute. The skip-rate monitor warns when a workflow's share of skipped runs over the trailing day exceeds 50 percent. Both monitors notify on recovery, and the accompanying README documents the mapping from workflow files to Datadog pipeline names, the import steps, and the assumptions that need to be verified in the CI Pipelines explorer before the monitors can be relied on.
eps1lon
force-pushed
the
sebbie/ci-workflow-health-monitors
branch
from
September 11, 2026 18:09
0a56500 to
077c11b
Compare
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
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 two import-ready Datadog monitor definitions under
scripts/datadog/workflow-health/covering the workflows that run without intentional user input: the scheduled (cron) workflows and the ones driven purely byworkflow_run,issues, orissue_commentevents. An audit of these workflows found that several had been failing unnoticed for weeks (four of them withstartup_failuresince 2026-08-21), which is the gap these monitors close.failure-monitor.jsonis a multi-alertci-pipelines alertthat notifies on the very first failed run of each workflow, with no consecutive-failure tolerance, and its message links the specific failed execution via theci.pipeline.urlattribute.skip-rate-monitor.jsonwarns when a workflow's share of skipped runs over the trailing day exceeds 95 percent and alerts at 100 percent, where every completed run was skipped, which usually means a condition broke and the workflow silently stopped doing work. Both monitors keep messages minimal, notify on recovery and on no data, and renotify once a week while they stay in a triggered state. For the skip-rate monitor, whose queries match every run, the no-data path also acts as the detector for the GitHub integration itself stopping to report.Nothing applies these definitions automatically. After merging, import each JSON via https://app.datadoghq.com/monitors/create/import and replace
@slack-TODOwith the real channel handle. The README lists the covered workflows (kept as a plain list so it can be re-derived from the trigger criteria) and the assumptions to verify in the CI Pipelines explorer before relying on the monitors: pipeline names match the workflow display names, skipped runs carry a distinguishable status,startup_failureruns surface as error events, and theci.pipeline.urlvariable renders a run URL in the alert message.