jambonz / jambonz/jambonz-api-server
Propagating alerts from jambonz webapp so our pagerduty can fire on them
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 38
- Avg merge
- 8h 34m
- Merged PRs (30d)
- 1
Description
We want to generate alerts in our pager duty based on alerts in the jambonz x/internal/alerts console. For instance, awhile back, we had a misconfiguration in the STT we were using, and it would show up on the alerts page like this:
`{"type":"invalid_model","reason":"Feature Validation Failed: lang pack [auto] is not supported"}`
This all well and good, but we want those to potentially trigger our pagerduty system is aware of them as soon as they occur.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the x/internal/alerts console and trace how alerts are generated and exposed. Then review the PagerDuty integration requirements and determine how an alert event should reach PagerDuty immediately. Done means alerts such as the invalid_model example can reliably trigger the PagerDuty system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100