Repository navigation
Alarm triage tie-in (1.2.0) - #2
Merged
Merged
Conversation
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.
The dashboard raises the alarm flood; the BMS Alarm Triage Agent cuts it to a short ranked list.
Backend
triage_export.py,GET /api/export/journal): alarm journal and trend history for a window in the agent'sbms-triage-journalv1 format: every alarm point with limit, deadband, priority and signal, the equipment topology, every journal entry, and the trend samples behind each point.GEN-1.RUNalarm (priority 4, "Generator running") so the generator start is in the journal.2060b45.Front end
/#/triage): root cause first, consequences collapsed under it, trend evidence chart with the limit and the time past it, the next step, and a label saying whether the template or Claude Haiku wrote the text. Lazy loaded (3.3 kB gzipped). Works at phone width with the bottom nav at seven tabs.Hosting
No Render dashboard changes and no API key. Without
TRIAGE_ANTHROPIC_KEYthe template writes the text, so the hosted demo uses the template.Simulated utility outage
24 journal entries (6 alarms, 6 returns, 12 acknowledgements and suppressions) come back as 1 ranked item: the utility failure, with UPS A and B on battery, generator running, ATS on emergency, and the generator frequency dip under it.
Tests