Documentation Observability
OBSERVABILITY / EXPERT

Alerts & telemetry freshness

Separate real failures from missing measurements and expected inactivity.

Avoiding false reassurance

An empty alert list can mean all rules are normal, a source is unreachable, rules are absent, or data is missing. The application must expose source failures and never infer universal health from that one list. Likewise, transport uptime and service correctness are independent signals.

Threshold duration

Sustained windows filter scheduler noise and short bursts. They should not delay fast availability alerts: a required service outage needs a shorter window than high CPU. Backup deadlines depend on schedule rather than a universal fixed duration.

Independent monitoring

The portal cannot reliably report its own total outage. Its external synthetic check and cloud alert evaluation form the independent failure detector. Notification routing remains in the existing provider rather than adding another competing alert engine.

ON THIS PAGE

THREE WAYS TO UNDERSTAND

Same system.
Your level of detail.

Switch reading modes above to find the explanation that fits.

Explore Technical →

Keep exploring

The observability portal

One organized interface for infrastructure and application evidence.

NutsNews service map

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