Microservice monitoring of SRE Golden Signals
Containerized applications share an intricate web of microservices that enable efficiency and portability but can make it difficult to isolate root causes when issues arise, especially when resources are deployed across hybrid environments. Monitoring the four standardized golden signals (latency, errors, traffic and saturation) quickly identifies the symptoms of a problem at the microservice level. Eliminating time-consuming discovery phase actions help teams deploy the proper resources to resolve issues quickly whether in VM, container or hybrid environments.
Tour
1. Get immediate notification of critical events in context
The incident view notifies the SRE of incidents occurring within applications and quickly provides detailed context at the microservice level.
2. Determine the scope of impact
Triage the incidents using the SRE golden signals. This end-user perspective of metrics at the microservice level allows anyone to troubleshoot an issue without having to be an expert in a service's individual code language.
3. Drill into additional detail for an affected service
Use the topology view to identify the exact point in time there was an issue with a microservice, Identify the issue and view the service in its previously healthy state to determine root cause.
4. Automate runbooks
Runbooks will be suggested automatically and may run directly from the context of the incident. Create a new runbook to automatically troubleshoot similar incidents.
