Logs
The Logs page shows a live window of structured log entries from the platform services. Open Monitoring, then Logs (/admin/monitoring/logs). It collects recent entries from the Core API, HEAT Auth and the v2 API, so you can triage a problem without shell access to the pods.
Reading the logs
The page streams entries with an auto-refresh toggle. Two controls narrow what you see:
- A filter box matches on text, and on fields such as a URL, a correlation id or a trace id.
- A severity selector shows all entries, errors and exceptions, or exceptions only.
Each entry can carry a url, a correlationId and a traceId. The correlation id ties together the log lines for one request across services, which is the fastest way to follow a single failing call.
The service log buffer is a short rolling window held in memory, so it is meant for quick triage. Entries older than the window are gone, and a pod restart clears its buffer. For a single service in depth, open its pod on the Cluster page and read the pod’s own logs.