Otel config reference

Author: Starefossen

docs/how-to-guides/observability/auto-instrumentation.md

@@ -57,3 +57,7 @@ spec:
       enabled: true
       runtime: sdk
 ```
+
+## Resources
+
+[:bulb: OpenTelemetry Auto-Instrumentation Configuration Reference](../../reference/observability/auto-config.md)

docs/how-to-guides/observability/tracing/context-propagation.md

@@ -1,3 +1,7 @@
+---
+description: Learn how to propagate trace context across process boundaries in a few common scenarios.
+tags: [guide, tracing]
+---
 # Trace context propagation
 
 Each Span carries a Context that includes metadata about the trace (like a unique trace identifier and span identifier) and any other data you choose to include. This context is propagated across process boundaries, allowing all the work that's part of a single trace to be linked together, even if it spans multiple services.

docs/reference/observability/auto-config.md

@@ -0,0 +1,27 @@
+# OpenTelemetry Auto-Instrumentation Configuration
+
+When you enable [auto-instrumentation](../../how-to-guides/observability/auto-instrumentation.md) in your application the following OpenTelemetry configuration will become available to your application as environment variables:
+
+| Variable                             | Example Value                                                                                 |
+| ------------------------------------ | --------------------------------------------------------------------------------------------- |
+| `OTEL_SERVICE_NAME`                  | `my-application`                                                                              |
+| `OTEL_EXPORTER_OTLP_ENDPOINT`        | `http://opentelemetry-collector.nais-system:4317`                                             |
+| `OTEL_EXPORTER_OTLP_PROTOCOL`        | `grpc`                                                                                        |
+| `OTEL_EXPORTER_OTLP_INSECURE`        | `true`                                                                                        |
+| `OTEL_PROPAGATORS`                   | `tracecontext,baggage`                                                                        |
+| `OTEL_TRACES_SAMPLER`                | `parentbased_always_on`                                                                       |
+| `OTEL_RESOURCE_ATTRIBUTES_POD_NAME`  | `my-application-777787df6d-pw9mq`                                                             |
+| `OTEL_RESOURCE_ATTRIBUTES_NODE_NAME` | `gke-node-abc123`                                                                             |
+| `OTEL_RESOURCE_ATTRIBUTES`           | `service.name=my-application,service.namespace=my-team,k8s.container.name=my-application,...` |
+
+!!! tip
+    Do not hardcode these values in your application. OpenTelemetry SDKs and auto-instrumentation libraries will automatically pick up these environment variables and use them to configure the SDK.
+
+## More OpenTelemetry Configuration
+
+A full list of environment variables that can be used to configure the OpenTelemetry SDK can be found here:
+
+* [:simple-opentelemetry: General SDK Configuration](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#general-sdk-configuration)
+* [:simple-opentelemetry: OTLP Exporter Configuration](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/)
+
+[OTLP is the OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/exporter/), and is the protocol used to send telemetry data to Prometheus, Grafana Tempo, and Grafana Loki.

docs/reference/observability/tracing/traceql.md

@@ -43,7 +43,7 @@ Similar to PromQL, TraceQL supports a set of operators for comparing span attrib
 
 Since a trace can be composed of multiple spans, multiple selectors can be used together to filter spans based on different attributes.
 
-TraceQL supports two types of combining spansets: logical (`&&` and `||`) and structural relations (`>`, `>>`, `<<` `<`, and `~`).
+TraceQL supports two types of combining spansets: logical (`&&` and `||`) and structural relations (`>`, `>\>`, `<\<` `<`, and `~`).
 
 ##### Logical
 
@@ -60,8 +60,8 @@ The above query will return traces where a span with the service name `server` a
 Structural relations are used to filter spans based on their structural relationships. The structural relations are:
 
 - `>` - Direct parent of
-- `>>` - Ancestor of
-- `<<` - Descendant of
+- `>\>` - Ancestor of
+- `<\<` - Descendant of
 - `<` - Direct child of
 - `~` - Sibling of
 

mkdocs.yml

@@ -93,6 +93,7 @@ plugins:
           'addons/wonderwall.md': 'security/auth/wonderwall.md'
           'device/update.md': 'how-to-guides/naisdevice/update.md'
           'how-to-guides/observability/tracing/otel-tracing.md': 'how-to-guides/observability/auto-instrumentation.md'
+          'reference/observability/otel/tracing.md': 'reference/observability/auto-config.md'
 markdown_extensions:
   - toc:
       permalink: True