Product
Patterns and anomalies, not just a tail of raw lines.
LogHouse groups recurring messages, tracks how those groups change, and highlights new, spiking, or missing patterns so investigations start with signal.
Pattern groups
| Pattern | Events | Change | First / last |
|---|---|---|---|
| Connection timeout to database <*> | 128k | +18% · anomaly | 14d / 2s |
| User <*> authentication failed | 9.4k | +380% · anomaly | 6h / 9s |
| HTTP request completed status=<*> | 4.1M | +2% | 90d / 1s |
New pattern detected
Payment gateway timeout after <*> ms
Appeared 37 minutes ago
Volume anomaly
Authentication failures are 4.8× above baseline
Pattern disappeared
Expected heartbeat events have not appeared for 12 minutes
What gets surfaced
- New pattern detected — a message template that did not exist in the baseline window.
- Volume anomaly — a known pattern well above or below its recent rate.
- Pattern disappeared — heartbeats or jobs that should still be logging.
FAQ
Do insights replace search?
No. Insights point you at the right cluster of events. Search and surrounding context still close the incident.