Menu

1 / 7

Reconstructing Microservice Topology at Incident Time

Reading 0:00
15s threshold

Working with microservices introduces an inherent ephemerality. Subcomponents change state and influence behavior frequently based on various conditions of the environment the system runs in. Incidents in production rarely happen against a stationary architecture.

A deployment can replace pods, a scheduler can move workloads, endpoints change, and service-to-service traffic may shift while an incident is still developing. The state of the service that an investigating engineer sees after pulling up dashboards may already differ from the state that produced the first symptoms. Any modern observability system can provide metrics, traces, and change logs for a root cause analysis.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.