Repository navigation
feat(observability): alert when a voice note is given up, stuck or undelivered - #250
Merged
Merged
Conversation
…delivered New indrasnet-voice group on the telemetry exporter's live voice gauges (TemporalCoordination#411): - IndrasVoiceNoteGivenUp (critical): a live voice note's transcription gave up in the last 24 h. 21 notes were lost this way 2026-10-17..11-14 unnoticed. - IndrasVoiceNoteWaitingTooLong (warning): oldest waiting note > 2 h for 10m. - IndrasVoiceDeliveryFailing (critical): a transcript delivery failed in 24 h (until 11-14 every delivery to a deleted Telegram chat failed silently). - IndrasVoiceMetricsMissing (warning): the exporter cannot read voice health. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…bids test_alert_rules_cover_loss_pressure_and_host_contention forbids "transcript" (and authorization/cookie/prompt/response_body) anywhere in the rules file, so no alert can be built around sensitive content. The voice alerts only used the word descriptively, but the guard is a substring check and it should stay strict: reworded to "voice-to-text" / "text". No rule logic changed. promtool: 36 rules, 52 cases pass; the guard test passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
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.
Why
Between 2026-10-17 and 2026-11-14, 21 live voice notes were given up without a transcript, and 27 transcript deliveries went to a deleted Telegram chat. Nobody noticed for a month: the transcription queue logged a warning and moved on. The operator's requirement is that every failure is visible, along with what it cost.
What
A new
indrasnet-voicegroup, built on gauges the IndrasNet telemetry exporter now publishes (anantham/TemporalCoordination#411):IndrasVoiceNoteGivenUpindras_voice_given_up_24h > 0: a voice note's transcription was given up in the last 24 hIndrasVoiceNoteWaitingTooLongIndrasVoiceDeliveryFailingindras_voice_delivery_failed_24h > 0: a transcript delivery failed in the last 24 hIndrasVoiceMetricsMissingThe 24-hour window means a new give-up alerts once, while the recovered historical ones don't page forever. Alerts reach the operator's Beeper Note to self through the fixed notifier (TC #404).
Verification
promtool check rulespasses (36 rules).promtool test rulescases pass, 7 of them new: given up / none given up; waiting 3 h / 30 min; delivery failed; metrics missing / OK.Not live until
🤖 Generated with Claude Code