From 5329ca1a89adb2b337b0440141914e9cca392b82 Mon Sep 17 00:00:00 2001 From: Tim Hingston Date: Fri, 6 Sep 2024 13:39:48 +1000 Subject: [PATCH] Add CTA for experimental OTel tracing. --- src/content/graphos/metrics/sending-operation-metrics.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/graphos/metrics/sending-operation-metrics.mdx b/src/content/graphos/metrics/sending-operation-metrics.mdx index 43a9bb2a1..d5ba1c7fd 100644 --- a/src/content/graphos/metrics/sending-operation-metrics.mdx +++ b/src/content/graphos/metrics/sending-operation-metrics.mdx @@ -50,7 +50,8 @@ Now, when your router or server starts up, it automatically begins reporting ope #### Enhanced reporting with the GraphOS Router -If you use the GraphOS Router to report operation metrics, you can configure [enhanced operation signature normalization](/router/configuration/overview/#enhanced-operation-signature-normalization) and [extended reference reporting](/router/configuration/overview/#extended-reference-reporting) for more comprehensive insights and operation checks. +- If you use the GraphOS Router to report operation metrics, you can configure [enhanced operation signature normalization](/router/configuration/overview/#enhanced-operation-signature-normalization) and [extended reference reporting](/router/configuration/overview/#extended-reference-reporting) for more comprehensive insights and operation checks. +- If you use the GraphOS Router to report traces to Studio, you can enable [enhanced tracing](/router/configuration/overview#enhanced-tracing-in-studio-via-opentelemetry) to get additional spans and attributes in traces. ### From a third-party server (advanced)