Domain-Specific
Web / HTTP Detection
Updated May 31, 2026 · today
4xx and 5xx surges, slow endpoints, TLS handshake failures, gateway timeouts, and load balancer health events.
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 for HTTP access logs (nginx, Apache, Envoy, ALB/NLB). Matches status code patterns, TLS errors, upstream timeouts, and health check failures. Works with standard combined/JSON access log formats. 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.
- 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.