observability-setup

Set up health checks and Prometheus metrics for a NAIS application by exposing standard isalive and isready endpoints alongside a metrics route. This provides repeatable readiness probes and metrics scraping for Kubernetes deployments.

Enable OpenTelemetry tracing in NAIS deployments by following auto-instrumentation guidance and adding tracing configuration to your Nais manifest. This integrates distributed tracing with minimal boilerplate for your service.

The best way to configure observability for a NAIS Kotlin service is applying a cohesive pattern that combines health endpoints, Prometheus metrics, OpenTelemetry tracing, and structured logging within your Nais manifest configuration.

Structured logging patterns are included as part of establishing NAIS observability. You implement these patterns alongside health endpoints and metrics exposure to ensure consistent log aggregation across services.

OpenTelemetry auto-instrumentation works with NAIS manifest configurations by adding specific observability settings to the deployment manifest. This enables tracing integration without requiring extensive manual code instrumentation.

NAIS health endpoints may fail readiness checks if isalive and isready routes are not properly exposed or configured. Implementing standard endpoint patterns ensures Kubernetes can accurately verify service availability and readiness.