Kubernetes Detection

Example alert

Exact wording varies — the detector generates titles from the anomaly it finds. This is representative of what an alert looks like when it fires.

How it works

Deterministic rule pack matching kubelet, scheduler, and event log patterns. Each rule targets a specific Kubernetes failure signature with regex + field conditions. Fires from the first matching log line — no learning period.

Availability

Runs on these tiers:

Related detectors

• AWS Service Detection

  Patterns for RDS, S3, DynamoDB, ECS, EKS, IAM, KMS, Lambda, and 20+ other AWS services. Catches throttling, capacity events, IAM denials, and service-specific failure modes.

• Serverless Detection

  Lambda timeouts, cold starts, throttling, init failures, runtime crashes, and concurrency limits across functions.

• Database Detection

  Connection pool exhaustion, deadlocks, slow queries, replication lag, schema migration errors, and transaction aborts across Postgres, MySQL, and MongoDB.

• Dependency Detection

  Upstream service failures, circuit breaker trips, retry exhaustion, and cascading failures between services.

• Web / HTTP Detection

  4xx and 5xx surges, slow endpoints, TLS handshake failures, gateway timeouts, and load balancer health events.