Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 5 days▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 12:18:26.
› →|
updated 1d ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.

Log alerts 0 on delta

Rules over the log lines X-ray reads from BigQuery. What a rule matches becomes one incident per error shape, with a count — never one message per line. ?Evaluated every minute over the error lines of the rule's clusters, refreshed from BigQuery first, so a line is at most a couple of minutes old. An incident closes once its shape has not appeared for the rule's window, and is delivered by the level rules (critical & high immediately, medium grouped, low in the digest). Namespaces read: tilda, neo4j-system, weaviate, external-secrets, cert-manager, keda, istio-system, kube-system, x-ray.

+ New log rule
Dry-run. Messages are composed and logged under Deliveries; nothing external is sent unless a channel was armed on its own.
No log rules on delta yet. Write the first one below — test it against the last hour before you save it.

New log rule

1 What to watch
Clusters
Namespaces — none ticked means every namespace
Log severity
2 Which lines
3 When it counts

At least matching line(s) within minutes opens an incident for that error shape.

4 How serious
5 Name it
It opens incidents; the level rules deliver them.