Add aria-alert-investigator skill for Aria health-metric IcMs, Fixes AB#3589793#428
Open
Add aria-alert-investigator skill for Aria health-metric IcMs, Fixes AB#3589793#428
Conversation
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
Adds a new skill at .github/skills/aria-alert-investigator/SKILL.md that handles Aria-detected anomaly IcMs (titles starting with 'Aria detected an incident in <project> for <metric>'). These alerts have a fundamentally different investigation pattern than customer-reported incidents: there is no customer, no error chain, and no log file, only 'the curve moved'. The new skill enforces evidence-first investigation with metric-slice confirmation, multi-angle trend analysis, and explicit separation of data findings from opinions. Also: - Register the skill in .github/copilot-instructions.md so the agent picks it up. - Add a pointer from the kusto-analyst skill so authors of Kusto queries delegate the Aria-specific workflow back here. - Fix two unrelated pre-existing typos in kusto-analyst SKILL.md (corrupted MATS table row and 'isspecified' missing space) that would otherwise show up in the same diff.
somalaya
force-pushed
the
skills/aria-alert-investigator
branch
from
25b34aa to
5b32dbf
Compare
somalaya
changed the title
|
✅ Work item link check complete. Description contains link AB#3589793 to an Azure Boards work item. |
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
1 participant
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 a new skill at
.github/skills/aria-alert-investigator/SKILL.mdthat handles Aria-detected anomaly IcMs (titles starting withAria detected an incident in <project> for <metric>).Why
These alerts have a fundamentally different investigation pattern than customer-reported incidents: there is no customer, no error chain, and no log file — only "the curve moved". The existing
incident-investigatorskill assumes customer-reported failures and produces wrong conclusions on Aria alerts. I have hit this several times now while triaging anomaly-detection IcMs.What the new skill enforces
codebase-researcherto understand what unfamiliar attributes/error codes mean.Other changes
.github/copilot-instructions.mdso the agent picks it up.kusto-analystSKILL.md so Kusto-query authors delegate the Aria-specific workflow back here.kusto-analyst/SKILL.md(corrupted MATS table row+------=+|andisspecifiedmissing space).Tested via
Used the new workflow end-to-end on IcM 786276130 (
TD - ATS Devices W/ SuccessAria alert) earlier today. Multi-angle trend correctly attributed the metric drop to the 14.2.0 broker rollout instead of the alert grain itself, matching the historical pattern from sibling ICMs.Fixes AB#3589793