Documentation Observability
OBSERVABILITY / EXPERT

NutsNews service map

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

Dependency health versus user impact

A queue, a worker, and a website expose different failure surfaces. Queue depth can rise during normal throughput bursts; errors can increase while fallback preserves availability. Combining expected ownership, queue age, terminal outcomes, and public synthetic checks prevents misleading incident conclusions.

Existing telemetry policy

NutsNews already defines a signal budget and permitted label taxonomy. Importing dashboards does not authorize unlimited new telemetry. Existing policy defers some trace and profile export. The portal exposes trace availability honestly and should not infer completeness merely from the presence of a Tempo datasource.

Source ownership

The central portal reads existing metrics rather than taking over every NutsNews provisioning pipeline. This avoids two repositories fighting over the same Grafana or server resource. New ownership is explicit; migrations require a single writer and a documented handoff.

Separate authentication from telemetry

A 401 means the browser needs a new owner session. Treat it independently from a source query failure or an empty series. Google ID verification and authorization happen on the portal server; Grafana tokens never enter the browser.

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.

Logs, traces & privacy

Find useful diagnostic evidence without exposing private records.