Platform · Platform

Telemetry

The Settings → Platform → Telemetry page shows where your Scrydon deployment sends traces, metrics and logs, whether each reaches your OpenTelemetry collector, and the Helm values that change it.

Telemetry shows how your Scrydon deployment exports traces, metrics and logs to your own OpenTelemetry collector. Open it from Settings → Platform → Telemetry. It is read-only: every setting on the page is a Helm value that the pods read when they start, so you change it in your values file and run helm upgrade. The page shows the values to set.

Telemetry is available to platform administrators only, because it shows the internal addresses of your collectors. Organization administrators who are not platform administrators do not see it.

What you see

One card per signal. Each card has a status, the settings in effect, and, where Helm controls the signal, the Helm values block to copy into your values file.

Card	What it covers
Service traces and metrics (OTLP/HTTP)	The OTLP/HTTP endpoint Scrydon's services export traces and metrics to (`observability.otlpHttpEndpoint`), and whether the platform pod can reach it.
Dapr sidecar traces	The Dapr sidecars' trace exporter, sampling rate and OTLP/gRPC endpoint (`dapr.tracing`), and whether the platform pod can reach it.
Dapr sidecar metrics	The port the sidecars serve Prometheus metrics on (`dapr.metricsPort`), and which scrapers network policies allow to read it.
Network path	Whether network policies are on, which workloads they isolate, and the collectors and scrapers the telemetry route admits (`networkPolicies.telemetry`).
Logs	Services write NDJSON logs to stdout. Your cluster's log agent collects them; Scrydon does not ship logs, and network policies do not affect that path.

Statuses

OK — the signal is configured and reaches its collector.
Off — nothing is configured for this signal.
Blocked — the signal is configured, but a network policy drops it before it reaches the collector. Add the collector to networkPolicies.telemetry; the Network path card shows the block to add, with your collector's namespace and ports filled in. See networkPolicies.telemetry.
Unreachable — the platform pod could not open a connection to the collector within three seconds. The card shows the error.
Misconfigured — the endpoint cannot be dialled as written, for example a host without a port.
Unknown — the Helm chart did not report its settings to the platform, for example after an upgrade of the platform image without a matching chart.

Reachability is tested from the platform pod

The page opens a TCP connection to each configured collector from the platform pod. Network policies select pods, so another workload can be cut off while the platform pod connects. The Network path card covers the other workloads: it reports Blocked whenever a workload that exports telemetry is isolated and the route does not admit the collector.

Re-checking

The page checks when it opens. Press Re-check to probe again, for example after a helm upgrade once the pods have restarted.

Up nextStorage ConfigurationWhere your organization's files are stored — the deployment's default store, or S3-compatible or Azure Blob storage of your own — and when files upload directly from the browser versus through the server.