You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With cos-alerter, we can only see if COSes are up or down at the moment, but not history about that (when did the outage start, how long did it last, is it reoccurring, etc.)
This should be made available to a remote COS through a relation, creating the dashboard automatically.
The text was updated successfully, but these errors were encountered:
COS Alerter is a watchdog service. The purpose is not to provide advanced monitoring capabilities. For what you are trying to achieve, I believe the best solution would be to deploy a second COS instance and have them monitor each other. This would give much more data than cos-alerter could ever provide.
Enhancement Proposal
With cos-alerter, we can only see if COSes are up or down at the moment, but not history about that (when did the outage start, how long did it last, is it reoccurring, etc.)
This should be made available to a remote COS through a relation, creating the dashboard automatically.
The text was updated successfully, but these errors were encountered: