Log Aggregation & APM
updated 07:37:43

Service Health

One screen tells you what is broken right now — across logs, metrics and traces.

Services up
2/3
Request rate
35.45/s
Error rate
4.8%
Worst p95
987ms
Request rate
req/s by service · 1h
Error rate
% of 5xx · 1h
Log volume
lines/min · all sources · 1h
Services
status · throughput · errors · latency · resources
Metrics →
ServiceStatusReq/sErrorsp50p95CPUMem
api2× restartOperational5.824.8%437ms987ms0.05124 MB
payments2× restartDegraded12.166.7%397ms911ms0.07132 MB
worker5× restartOperational17.473.4%192ms574ms0.06129 MB
Active incidents
auto-detected · 6h
All →
  • api restarted 2×
    Process start time changed 2 time(s) in the last 6h.
    0s ago
  • payments restarted 2×
    Process start time changed 2 time(s) in the last 6h.
    0s ago
  • victoriametrics restarted 2×
    Process start time changed 2 time(s) in the last 6h.
    0s ago
  • worker restarted 5×
    Process start time changed 5 time(s) in the last 6h.
    0s ago
  • postgres-yckw0wkg8k4co0osg8kwco0k-145449955773 crashed
    2026-06-09 07:37:41.695 UTC [939914] FATAL: database "cid_user" does not exist
    1s ago
  • postgres-yckw0wkg8k4co0osg8kwco0k-145449955773 crashed
    2026-06-09 07:36:55.991 UTC [939850] FATAL: database "cid_user" does not exist
    47s ago