-
Notifications
You must be signed in to change notification settings - Fork 525
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
processor/otel: extend support for OpenTelemetry semantic conventions #4711
Conversation
If the main "URL" input does not contain a scheme, use the given scheme parameter.
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Steps errorsExpand to view the steps failures
|
Extend our support for OpenTelemetry semantic conventions.
569eaa8
to
78207c3
Compare
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.
Didn't run it, but LGTM. That's going to be a lot of fields for testing...
…elastic#4711) # Conflicts: # changelogs/head.asciidoc
…elastic#4711) # Conflicts: # changelogs/head.asciidoc
Tested with BC 2 - works as expected. Tested with the otel |
Motivation/summary
Extend support for OpenTelemetry semantic conventions to cover what we support for traces in the OpenTelemetry Collector exporter, minus support for "exception" span events. These will be covered in a followup.
A couple of functional changes for the existing Jaeger support:
Checklist
- [ ] Documentation has been updated[OTLP] Document support for OTLP/gRPC on the standard port #4678How to test these changes
Related issues
#4503