Req 2.3 - Kea Degradation Canary
As an administrator, I need a clear visual indicator when a Kea server/service is becoming overloaded. This alerts me that I need to take some action to prevent further degradation or failure of the service.
As an administrator, if this alarm occurs frequently I would like to be able to customize the level that constitutes an alarming value. If there is a separate panel of alerts or logged events, I would expect to see these threshold-crossing alarms included there. It would be ideal if this is available without requiring that I install Grafana or Prometheus, as I may have a small deployment of one or two servers.
possible use cases:
- increasing
secs
reported by clients - users with external lease db, query to see how long it takes the db to do a select to see if the db itself, or the connection to the db is degraded
- any sort of statistics about the ring buffer, to alert when the buffer is growing excessively (this might be possible with the Stork agent but not with Kea)
- something that could help people detect conflicts when they are running multiple Keas with the same address range, using a shared lease db, because these can also lead to cascading performance issues
Details
- We will need to decide what metric or combination of metrics to base this alarm condition on.
- We discussed the fact that increasing delay in responding to client requests might be an indicator of a service degradation and a leading indicator of Kea server failure.