Open casperdcl opened 1 month ago
Think that this is an implementation specific thing => should be handled in the respecitive PRs that need it or benefit from it.
The cases you mentioned can either be considered as
UP
=> no notification orDOWN
=> issue notification=> don't currently see an iminent need for adding another status
sure, but it would be nice to have finer-grained severity options
see e.g.
📑 I have found these related issues/pull requests
123 added an
Accepted Status Code
field (to mark services as "Up")819 discusses "Up but at risk" services
🏷️ Feature Request Type
Change to existing monitor
🔖 Feature description
It would be great to have a
Degraded Status Code
field too (to mark services as "Pending"/"Maintenance"/"Slow" rather than "Down")✔️ Solution
Add a
Degraded Status Code
field toHTTP(s)
monitors