Documentation ›Observability
OBSERVABILITY / TECHNICAL

Alerts & telemetry freshness

Separate real failures from missing measurements and expected inactivity.

Default additions

Local-server checks cover missing telemetry, required service failure, CPU or memory above 90% for ten minutes, disk usage above 85% for fifteen minutes, and overdue backups using their actual schedule.

Existing rules

Retain current NutsNews thresholds and notification routing. The portal queries the existing Grafana alert source and distinguishes query failure from an empty active-alert list.

Freshness

Metric results with no samples are unavailable. Samples older than three minutes are stale in the portal. The HTTP response timestamp describes retrieval time, not necessarily measurement time.

Verification

Test new alert expressions with representative synthetic inputs. Verify recovery as well as firing, and avoid intentionally disrupting production services for routine validation.

Complete rule catalog

The public Alert rules page lists configured rules, including healthy and paused rules. It reads actual evaluation intervals from Cloud rule-group metadata; observed groups evaluate every 60 or 300 seconds. Pending duration and lookback are separate fields. Silenced rules remain enabled unless paused. Private expressions require owner diagnostics. Missing evaluation metadata is shown as unknown rather than inferred from query resolution.

ON THIS PAGE

THREE WAYS TO UNDERSTAND

Same system.
Your level of detail.

Switch reading modes above to find the explanation that fits.

Explore Expert →

Keep exploring

NutsNews service map

Follow the application from its public endpoints to workers and data services.

↗
Logs, traces & privacy

Find useful diagnostic evidence without exposing private records.

↗