[detection-analysis] Detection Analysis Report — 2026-07-08 (last 24h) #44302
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #44557. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
2026-07-08T07:13:40Z→2026-07-08T12:59:42ZWarning
7 workflows show detection-related misconfigurations. Detection-enabled runs have a higher success rate (83.8%) than regular runs (73.3%), but several audit/analysis workflows are missing the
gh-aw-detection: trueflag, and two active workflows (Smoke CI, Avenger) are failing consistently.Note
The
logsdownload timed out mid-transfer, so this is a partial capture (97 of the runs in the window carried complete metadata). Figures reflect the captured subset. Misconfiguration criterion#1(>3 runs over 7 days) is approximated against the captured window since only a partial 7-day history was available.Comparison Chart
Misconfigured Workflows
gh-aw-detection: false, 8 runs, all failing)gh-aw-detection: trueunless there is a documented reason to keep it off.gh-aw-detection: trueso detection safeguards apply.gh-aw-detection: trueto this analysis workflow.gh-aw-detection: trueto this audit workflow.gh-aw-detection: trueto this analysis workflow.View All Run Metrics
Detection column: on = all runs
gh-aw-detection: true; off = explicitlyfalse; absent = flag unset; mixed = inconsistent across runs.View Historical Trend
12 days of history (2026-06-27 → 2026-07-08). Detection-enabled run counts have trended upward (0 → 37/day) while the detection success-rate band has held in the 80–95% range. Regular-run success rate dipped to 73.3% today — the lowest in the window — driven largely by the fully-failing Smoke CI runs.
Recommendations
gh-aw-detection: true. Add the flag in frontmatter and recompile the.lock.yml.logstimeout to capture the full 24h set; today's partial capture may under-count failures and misconfigurations.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions