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
instrumented 3 go services on my side with a postgres on the back using Beyla. I am simply forwarding the traces to the alloy running with the k8s monitoring helm chart which forwards those to GC. Span metrics are being generated in GC using the trace metrics generator.
Tested with Alloy 1.5.0
most traces are OK (first image) but there are other traces that have lost their parent span. That's why they don't have any span attribute.
We need to see if Beyla is failing to relate the spans, but maybe there is also the possibility that the spans are lost in the way.
The text was updated successfully, but these errors were encountered:
Hi,
I have a customer ticket where their spans from python opentelemetry sdk do not have span attributes either. They are using grafana-k8s-monitoring, but since their resource attribute for sdk name is { "value": "opentelemetry", "key": "telemetry.sdk.name"} I am not sure if it is related to Beyla.
instrumented 3 go services on my side with a postgres on the back using Beyla. I am simply forwarding the traces to the alloy running with the k8s monitoring helm chart which forwards those to GC. Span metrics are being generated in GC using the trace metrics generator.
Tested with Alloy 1.5.0
most traces are OK (first image) but there are other traces that have lost their parent span. That's why they don't have any span attribute.
We need to see if Beyla is failing to relate the spans, but maybe there is also the possibility that the spans are lost in the way.
The text was updated successfully, but these errors were encountered: