-
Notifications
You must be signed in to change notification settings - Fork 820
Create OpenTelemetry Bridge for Tracing #4834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# enhance exporter with attributes for specific exporter. Currently only | ||
# awsxray is supported | ||
# CLI flag: -tracing.otel.exporter-type | ||
[exporter_type: <string> | default = ""] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does default "" mean awsxray?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No.. defaults mean "generic"...
What we do here for some destinations we need to configure the exporter a little different. For instance, if the end backend is X-Ray we need to generate the traceIds in a specific format.
I believe for the majority of the backends it will work with this type set to empty.
cbec84e
to
9c6e384
Compare
Signed-off-by: Alan Protasio <approtas@amazon.com>
Signed-off-by: Alan Protasio <approtas@amazon.com>
Signed-off-by: Alan Protasio <approtas@amazon.com>
Signed-off-by: Alan Protasio <approtas@amazon.com>
Signed-off-by: Alan Protasio <approtas@amazon.com>
Signed-off-by: Alan Protasio <approtas@amazon.com>
What this PR does:
Create OpenTelemetry Bridge for Tracing following https://opentelemetry.io/docs/migration/opentracing/
With this PR we can now export Cortex traces to multiples destinations as, for example, AWS X-RAY:
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]