Observability

Platon's observability platform is built on the Grafana stack, with Loki for logs, Mimir for metrics and Tempo for traces. You access all three through grafana.platon.sikt.no.

Platon supports two ways to use the platform: logging only, or full observability with OpenTelemetry.

Logging only

For teams that have a working logs-centric setup, or who are not (yet) adopting OpenTelemetry (OTel).

Start here if:

• You run on Platon PaaS and logging is all you need. See PaaS Logging.
• You run on Puppet-managed VMs. See Puppet-managed VMs.
• You run outside Platon and want to ship logs in. See External Services.

Reference material: Logs, LogQL best practices, Alerting.

Full observability with OpenTelemetry

For teams that want metrics and traces in addition to logs. OpenTelemetry is a vendor-neutral standard for producing this telemetry, and Platon's observability platform receives it without translation.

Start here if:

• You are new to OpenTelemetry and want a short orientation. See OpenTelemetry tutorial.
• You already know OTel and only need the Platon-specific setup. See PaaS Full Observability or External Services.

Reference material: Choosing your signals, Logs, Metrics, Traces, Alerting.

Kubernetes metrics on PaaS

Every Platon PaaS workload emits Kubernetes metrics (CPU, memory, pod restarts) to Mimir without any setup. They appear in your team's Grafana organization and in shared dashboards in the "Sikt" Grafana organization. See Metrics — What you get for free on Platon PaaS.

Access Grafana

Go to grafana.platon.sikt.no. You are automatically logged in with Entra ID. You will land in your team's Grafana organization, and if you belong to more than one, you can switch between them.