Observability platform
c4v1/01 Views
/02 About
Services emit metrics, logs and traces to a telemetry collector that routes them to purpose-built stores, dashboards and alerting.
Every service emits the three signals in a standard format to a collector, which enriches, samples and routes them. Each signal lands in a store suited to it, and dashboards and alerts are built on service-level objectives rather than raw thresholds. When to use: any distributed system in production, and certainly microservices, event-driven and serverless systems where a request crosses many components. Trade-offs: faster diagnosis and measurable reliability; telemetry volume and cost grow quickly, so sample traces, control log levels and set retention per signal. Keep sensitive data out of logs.
Published by Lattix · 9 elements · 11 relationships · validated on publish
/03 Contents
- Application Component
- Service A, Service B, Alerting
- System Software
- Telemetry collector
- Data Store
- Metrics store, Log store, Trace store
- Application
- Dashboards
- Role
- On-call engineer