New Ory Agent Security is now live! Claim your complimentary test drive. Get Started!

Skip to main content

v26.4.0

v26.4.0​

OpenTelemetry metrics follow the standard protocol and configuration​

Ory Polis now sends OpenTelemetry metrics in the protocol you configure. OTEL_EXPORTER_OTLP_METRICS_PROTOCOL and OTEL_EXPORTER_OTLP_PROTOCOL accept grpc, http/protobuf and http/json; the metrics-specific variable takes precedence. Previously only grpc was honored and every other value, including http/protobuf, sent OTLP over HTTP/JSON.

The export schedule can now be set with the standard OTEL_METRIC_EXPORT_INTERVAL and OTEL_METRIC_EXPORT_TIMEOUT variables, in milliseconds, and the SDK's own diagnostic logging with OTEL_LOG_LEVEL. The previous OTEL_EXPORT_INTERVAL_MS and OTEL_EXPORTER_DEBUG variables are deprecated but still work when the standard ones are unset.

Metrics are now flushed when Polis receives SIGTERM or SIGINT, so the values recorded since the last periodic export are no longer lost on shutdown.

See Environment variables.

Breaking changes​

When neither protocol variable is set, metrics are now sent as http/protobuf, the OpenTelemetry default, instead of http/json. If your collector accepts only JSON, set OTEL_EXPORTER_OTLP_METRICS_PROTOCOL=http/json before upgrading.

If you set OTEL_EXPORTER_OTLP_METRICS_PROTOCOL=http/protobuf, which the polis-oel Helm chart does by default, Polis now sends protobuf as configured rather than JSON. This is the correct behavior, but a collector that was relying on receiving JSON at that endpoint needs to accept protobuf.