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
Nonetheless OpenTelemetry trace ids and X-Ray trace ids are compatible, because both can be stored as a 128 bit integer.
What is the proposed solution?
This plugin should try to automatically convert from OpenTelemetry trace ids to X-Ray trace ids when you click in the button in the dialog from the image above.
This can be an optin feature.
The text was updated successfully, but these errors were encountered:
As an additional information for this – the AWS X-Ray console automatically allow searches with the X-Ray trace id format and the OpenTelemetry (W3C) trace id format. So now it's only Grafana which doesn't do this.
What is my problem?
In an application that uses OpenTelemetry and generate exemplars and traces, the trace id will be presented in the form of a 128 bit hex string.
However the X-Ray trace id format is different: https://docs.aws.amazon.com/xray/latest/devguide/xray-api-sendingdata.html#xray-api-traceids
Nonetheless OpenTelemetry trace ids and X-Ray trace ids are compatible, because both can be stored as a 128 bit integer.
What is the proposed solution?
This plugin should try to automatically convert from OpenTelemetry trace ids to X-Ray trace ids when you click in the button in the dialog from the image above.
This can be an optin feature.
The text was updated successfully, but these errors were encountered: