-
Notifications
You must be signed in to change notification settings - Fork 890
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
add console as a supported env variable exporter type #3742
add console as a supported env variable exporter type #3742
Conversation
This adds support for the standard output exporter for traces and metrics. To remain consistent with other implementations, i used the key `console` as the identifier for the exporter. This change is related to the specification pull request open-telemetry/opentelemetry-specification#3742 Signed-off-by: Alex Boten <[email protected]>
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.
Just the changelog entry should be moved
Note to reviewers that |
This adds support for the standard output exporter for traces and metrics. To remain consistent with other implementations, i used the key `console` as the identifier for the exporter. This change is related to the specification pull request open-telemetry/opentelemetry-specification#3742 Signed-off-by: Alex Boten <[email protected]>
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
For completness: Following the spec compliance matrix the following languages have support for OTEL_TRACES_EXPORTER and besides I listed how an enduser can set the console exporter:
Rust, C++, Go and Swift are listed with not supported/unknown. .NET is also listed as not supported, but the .NET auto instrumentation has the following construct (see https://opentelemetry.io/docs/instrumentation/net/getting-started/ & https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/config.md#internal-logs):
|
Go will add support for |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
This PR is a follow up to open-telemetry#3740 and open-telemetry#3741. As some languages (the ones I looked at were: python, js, ruby) already support the `console` type of exporter, I thought it would be good if the spec confirmed it. Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
15892d7
to
1fcefba
Compare
Co-authored-by: Tyler Yahn <[email protected]>
Co-authored-by: Tyler Yahn <[email protected]>
Co-authored-by: Tyler Yahn <[email protected]>
…#3742) ## Changes This PR is a follow up to open-telemetry#3740 and open-telemetry#3741. As some languages (the ones I looked at were: python, js, ruby) already support the `console` type of exporter, I thought it would be good if the spec confirmed it.
Changes
This PR is a follow up to #3740 and #3741. As some languages (the ones I looked at were: python, js, ruby) already support the
console
type of exporter, I thought it would be good if the spec confirmed it.CHANGELOG.md
file updated for non-trivial changesKeeping in draft until the other PRs are reviewed.