Domain-Specific
Database Detection
Updated May 31, 2026 · today
Connection pool exhaustion, deadlocks, slow queries, replication lag, schema migration errors, and transaction aborts across Postgres, MySQL, and MongoDB.
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
Rule pack matching database engine log patterns — Postgres pg_log, MySQL error/slow logs, MongoDB mongod logs. Detects deadlocks, lock waits, replication lag, connection exhaustion, and migration failures. No learning period.
Availability
Runs on these tiers:
Want to see this detector firing in the live demo?
Open alerts in the sandbox →Related detectors
- Kubernetes Detection
70+ rules for OOMKilled, CrashLoopBackOff, ImagePullBackOff, FailedScheduling, evictions, probe failures, and other Kubernetes failure modes.
- 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.
- 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.