Drill into health & metrics of each affected service

In our Redis example, you can click on the heart symbol under the Redis event in the event log to access the Redis service health screen:

The Redis service health page shows the same issue, as well as a red status on one of the service instances shortly after the service anomaly:


The Redis service metrics page shows that the Redis service on one of the hosts stopped sending data after a burst of commands were processed. Most likely the Redis service instance on that host died:


Follow up this investigation with a confirmation of root cause using service cluster and host level system metrics.


If you have any questions or comments about this article, feel free to contact us at support@opsclarity.com.

2016.2.4 0.8.111

Have more questions? Submit a request


Please sign in to leave a comment.