From 9f1c701fd1d927fbb32e0cb294c4315a1b959838 Mon Sep 17 00:00:00 2001 From: Peter Bourgon Date: Fri, 25 Jul 2025 17:49:46 +0200 Subject: [PATCH 1/2] operate/monitoring/tracing: mention otlp+http --- docs/operate/monitoring/tracing.mdx | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/operate/monitoring/tracing.mdx b/docs/operate/monitoring/tracing.mdx index 1ded467ea..eaaaed05b 100644 --- a/docs/operate/monitoring/tracing.mdx +++ b/docs/operate/monitoring/tracing.mdx @@ -20,19 +20,20 @@ Set up the [OTLP exporter](https://github.com/open-telemetry/opentelemetry-colle ### Exporting traces to Jaeger -[Jaeger](https://www.jaegertracing.io/docs/2.4/deployment/) accepts OTLP trace data on port `4317`. +[Jaeger](https://www.jaegertracing.io/docs/2.4/deployment/) accepts OTLP trace data on port `4317` (gRPC) and `4318` (HTTP). Start Jaeger locally with Docker, for example: ```shell docker run -d --name jaeger \ - -p 4317:4317 -p 16686:16686 \ + -p 4317:4317 -p 4318:4318 -p 16686:16686 \ jaegertracing/jaeger:2.4.0 ``` -Configure the tracing endpoint in Restate as a fully specified URL: +Configure the tracing endpoint in Restate as a valid URL: ```shell -restate-server --tracing-endpoint http://localhost:4317 +restate-server --tracing-endpoint http://localhost:4317 # for gRPC +restate-server --tracing-endpoint otlp+http://localhost:4318/v1/traces # for HTTP (note the /v1/traces path) ``` If you run Restate in Docker, then instead add the environment variable `-e RESTATE_TRACING_ENDPOINT=http://host.docker.internal:4317`. From 7ba974281f275cc8e493269a5b5e9a2cc6452117 Mon Sep 17 00:00:00 2001 From: Peter Bourgon Date: Mon, 28 Jul 2025 09:47:04 +0200 Subject: [PATCH 2/2] Update tracing.mdx --- docs/operate/monitoring/tracing.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/operate/monitoring/tracing.mdx b/docs/operate/monitoring/tracing.mdx index eaaaed05b..8c910d870 100644 --- a/docs/operate/monitoring/tracing.mdx +++ b/docs/operate/monitoring/tracing.mdx @@ -17,6 +17,9 @@ Restate supports the following tracing features: ## Setting up OTLP exporter Set up the [OTLP exporter](https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/otlpexporter/README.md) by pointing the configuration entry `tracing-endpoint` to your trace collector. +By default, a `tracing-endpoint` using the `http://` or `https://` scheme will emit trace data in the OTLP/gRPC format. +Restate also supports the `otlp+http://` and `otlp+https://` schemes, to emit trace data in the OTLP/HTTP format. +Note that when using OTLP/HTTP, the `tracing-endpoint` URI usually needs to include an e.g. `/v1/traces` path. ### Exporting traces to Jaeger @@ -33,7 +36,7 @@ Configure the tracing endpoint in Restate as a valid URL: ```shell restate-server --tracing-endpoint http://localhost:4317 # for gRPC -restate-server --tracing-endpoint otlp+http://localhost:4318/v1/traces # for HTTP (note the /v1/traces path) +restate-server --tracing-endpoint otlp+http://localhost:4318/v1/traces # for HTTP (note /v1/traces) ``` If you run Restate in Docker, then instead add the environment variable `-e RESTATE_TRACING_ENDPOINT=http://host.docker.internal:4317`.