Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,960 questions
Possibility to disable injection of traceparent in requests to WebApp
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 21%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBC%3C/text%3E%3C/svg%3E)
Brehmer, Christian
21
Reputation points
Hi,
lately we've noticed that our openTelemetry setup / tracing inside a webapp broke. While azure healthcheck requests to /robots933456.txt were still recorded correctly, everything else went silent (while running local tests or in other environments was working fine).
After quite some debugging, talking with the otel-js devs we found out, that Azure apparently started injecting a traceparent header in the requests that were send to the app and since this the ending flag (trace Flag) on this was 00 the recording of the following child traces was disabled/stopped.
While we've found a workaround for this, it still kind of breaks our tooling which complains about missing trace data/spans. Since another dev joined the discussion with the same problems but another language/platform (.NET) i feel like i should pursue this topic and ask here if there is any way to disable the injection of the traceparent header in the requests?
While we didn't actually document the changes in behavior on the azure apps, the second dev did:
2022-06-09 23:30 UTC - three apps stopped sending most OTel data (same app, different envs; we never do something to multiple envs at once)
2022-06-15 05:25 UTC - three apps resumed sending all OTel data
2022-06-18 00:00 UTC - two apps stopped sending most OTel data
2022-07-13 18:10 UTC - the remaining app stopped sending most OTel data
Another question would be if there is any source of information that would describe such changes in advance so that we could in the future possibly mitigate such problems.
For further info, you can follow the (closed) issue/conversation here: https://github.com/open-telemetry/opentelemetry-js/issues/3057
I'd appreciate any hints, thanks a lot in advance
kind regards
Christian
Azure App Service
{count} votes
-
brtrach-MSFT 17,741 Reputation points Microsoft Employee Moderator2022-07-25T02:54:54.663+00:00 @rumbleBreChr We apologize for the issue that you have been encountering with your tracing. There was a patch rolled out to address a separate issue, which seems to have caused this behavior. Our rollouts are done by region, so if you have apps in different regions, this might explain why all your apps tracing didn't stop at once.
We have reached out to the product group to determine if the injection of traceparent header information is intended with the most recent patch and if so, is there a way to disable it.
Please give us a day or so to hear back, at which point we will update you.
-
Brehmer, Christian 21 Reputation points
2022-08-02T11:39:36.283+00:00 -
brtrach-MSFT 17,741 Reputation points Microsoft Employee Moderator
2022-08-08T15:26:27.53+00:00 @Brehmer, Christian We just wanted to follow up that the hotfix for this issue should have just completed.
We apologize for the delay in alerting you, but the rollout took longer than expected and since you have apps in multiple regions, we wanted to ensure it was completed in all of the regions.
Please reply back here if you are still having further issues so we can assist you further.
Sign in to comment
Sign in to answer