observability
28 pagesAlerting
Alerting is a crucial part of observability, and it's the first step in knowing when something is wrong with your application.
Correlate traces and logs
Learn how to correlate traces with logs in Grafana Tempo.
Create a dashboard in Grafana
Create a dashboard in Grafana for your application
Create alert in Grafana
Learn how to create an alert for your application in Grafana.
Create alert with Prometheus
Create alerts for your application using Prometheus.
Customize Prometheus alerts
Advanced guide to customized Prometheus alerts
Disable persistent application logs
Disable log storage for a specific application
Distributed Tracing
Application Performance Monitoring or tracing using Grafana Tempo on Nais.
Expose metrics from your application
Expose metrics from your application
Frontend apps
Nais offers observability tooling for frontend applications. This page describes how to use these offerings.
Get started with auto-instrumentation
Get started with auto-instrumentation for your applications with OpenTelemetry data for Tracing, Metrics and Logs using the OpenTelemetry Agent.
Get started with Grafana Loki
Get started with Grafana Loki, the default and preferred log aggregation system for all Nais application
Get started with Grafana Tempo
Grafana Tempo is an open-source, easy-to-use, high-scale, and cost-effective distributed tracing backend that stores and queries traces in a way that is easy to understand and use. It is fullyβ¦
Get started with Team Logs
Get started with Team Logs, a private logging solution leveraging Google Cloud Logs.
Getting Started with Observability in Nais
This tutorial will guide you through the process of enabling observability for your application on Nais, using OpenTelemetry and the Grafana stack (Loki, Tempo, Prometheus, Grafana).
Instrumenting Your Application with OpenTelemetry
This tutorial shows how to add custom spans and metrics to your application when you are already using OpenTelemetry auto-instrumentation in Nais.
Logging
Logs are a way to understand what is happening in your application. They are usually text-based and are often used for debugging. Since the format of logs is usually not standardized, it can be difficult to query and aggregate logs and thus we recommend using metrics for dashboards and alerting.
Metrics
Metrics are a way to measure the state of your application and can be used to create alerts in Prometheus and dashboards in Grafana.
Observability
Nais offers several methods for monitoring and observing your applications. This page describes the different options and how to use them.
Observability Glossary
Observability is the art of understanding how a system behaves by adding instrumentation such as logs, metrics, and traces.
OpenTelemetry Auto-Instrumentation Configuration
When you enable auto-instrumentation in your application the following OpenTelemetry configuration will become available to your application as environment variables:
OpenTelemetry Metrics
This is a list of metrics exported by the OpenTelemetry SDKs and auto-instrumentation libraries. The OpenTelemetry SDKs and auto-instrumentation libraries export the following general metrics:
OpenTelemetry Trace Semantic Conventions
OpenTelemetry Trace Semantic Conventions can be found at opentelemetry.io.
Prometheus Alerting Rule Reference
PrometheusRule resource specification for defining alerts in Prometheus.
Push metrics to Prometheus
Push metrics to Prometheus
Span Metrics
Span metrics are collected for each span and provide insight into the performance of your application. On our platform, these metrics are generated by the Grafana Tempo metrics generator and exportedβ¦
Trace context propagation
Learn how to propagate trace context across process boundaries in a few common scenarios.
View logs from the command line
View logs from the command line using kubectl.