Monitoring
System monitoring and alerting
Best Practices
RED & USE Monitoring Methodologies
Standard approaches for selecting golden signals (Rate-Errors-Duration / Utilisation-Saturation-Errors).
by Google SRE & Brendan GreggThe Four Golden Signals
Google SRE's four core metrics for monitoring a user-facing system: latency, traffic, errors, and saturation.
by Google SREStructured Logging
Emitting logs as machine-parseable key-value records (typically JSON) with consistent fields, so logs can be searched, filtered, and correlated at scale.
by OpenTelemetry (CNCF)Prometheus Monitoring Best Practices
Guidance for naming metrics, controlling label cardinality, and writing alerting rules in Prometheus, the CNCF metrics and alerting system.
by Prometheus (CNCF)Symptom-Based Alerting
Alerting on user-visible symptoms (errors, latency, SLO burn) rather than internal causes, to reduce noise and page only on things that matter.
by Google SREObservability-Driven Development
Building instrumentation into software as a first-class part of development so engineers can ask new questions of production behavior without shipping new code.
by CNCFLLM Observability
LLM observability is the practice of tracing, logging, and measuring LLM applications in production to monitor quality, cost, latency, and safety and to debug failures.
by Cloud Native Computing Foundation (OpenTelemetry)Products & Technologies
Prometheus
Monitoring system with time series database
Grafana
Analytics and monitoring platform
Datadog
Cloud monitoring and security platform
New Relic
Observability platform for full-stack visibility