You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
We recently updated projects from Orleans 8.0 to 8.2 and we noticed that our Otel traces are mixed up. We have traces with thousands of spans. It seems that persistent pulling agents always reuse the same TraceId/OperationId as you can see in the screenshots below. The only significant change I see between 8.0 and 8.2 in the persistent pulling agent is the new Grain Timers. Could it be related?
Screenshot of Application Insights in Azure Portal:
The text was updated successfully, but these errors were encountered:
Costo
changed the title
Open Telemetry traces are all mixed up in Orleans 8.2 and up.
Orleans 8.2 and up creates OpenTelemetry traces with thousands of spans
Jan 6, 2025
Hi!
We recently updated projects from Orleans 8.0 to 8.2 and we noticed that our Otel traces are mixed up. We have traces with thousands of spans. It seems that persistent pulling agents always reuse the same TraceId/OperationId as you can see in the screenshots below. The only significant change I see between 8.0 and 8.2 in the persistent pulling agent is the new Grain Timers. Could it be related?
I created a reproduction project using the Simple Streaming Sample:
https://github.com/Costo/orleans-otel-issue/tree/main
Thanks!
Screenshot of Aspire Dashboard:
Screenshot of Application Insights in Azure Portal:
The text was updated successfully, but these errors were encountered: