-
Notifications
You must be signed in to change notification settings - Fork 825
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
Console exporter initialization via console
value for OTEL_TRACES_EXPORTER is not documented.
#4262
Comments
Hmm, interesting - thank you for opening this issue. It's not part of opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#exporter-selection beacuse the specifiction does not include 'console' as a known value to instanitate a console exporter. Strictly speaking we could remove it, but I think it is a useful feature to have. There's a few options that we could handle this:
@dnutels do you have a specific preference for one of the solutions listed above? 🤔 |
I would certainly be against removing it... My semi-coherent thoughts to follow. Consider an adoption process of OTEL in an application. It's quite possible that having the telemetry signals be sent to the console during the initial (and perhaps even past that) development is easier than having them being sent to a local collector (docker-composed or otherwise). In some languages (JavaScript/Python, at least) this would also simplify debugging as you adopt/develop (since it's all in-proc). Finally, if you do use a local collector over Docker (which would probably be the default for most) ... you pay with your machine resources as Docker needs to be running. So, having said that, and considering that we do have other quite odd values permitted ( It would be especially useful for logs, IMO. I wonder now if it should be a more general Then, you'd be able to cover console with Of course, it may be awkward due to the |
Yep, I can tell from experience that this is the usual way.
Certainly.
I agree needing a collector to run locally is overkill.
I think this is a great idea. I think that there's currently no specification for a trace or logs console exporter, so that is somthing that would have to be done as a prerequisite of that change. I was only able to find the spec for the metrics stdout exporter https://github.com/open-telemetry/opentelemetry-specification/blob/d855249b210ecd832889fc4ce91a4444f82e252a/specification/metrics/sdk_exporters/stdout.md?plain=1#L2 I currently do not have the bandwidth to drive this topic as we have other-higher priority items on the agenda, but I'd appreciate if you'd open an issue on the spec repo (or comment on an existing one, if applicable) and add the case there.
Do you mean having support for setting the exporters via environment variables for all signals? There's currently #3871 to track this if I understand this sentence correctly.
Do you mean an OTLP file exporter? There is a spec for that but I think it's mainly intended for the collector. If there's enough people that would be interested in this, and a good description of use-cases, we could certainly discuss adding it to this repo in a new issue.
You don't have to set only |
Already there: open-telemetry/opentelemetry-specification#3742 So perhaps close this once the PR drops? Your call. |
Great 🙂
Let's do that 🙂 I applied the |
Closing as the spec-PR has merged 🙂 |
What happened?
Steps to Reproduce
Application from: https://opentelemetry.io/docs/instrumentation/js/getting-started/nodejs/
Module configuration from https://opentelemetry.io/docs/instrumentation/js/automatic/
Expected Result
Traces sent to console.
Actual Result
Traces sent to console, but the
console
value forOTEL_TRACES_EXPORTER
is not documented here:https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#exporter-selection
despite appearing here:
https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/metapackages/auto-instrumentations-node/test/register.test.ts
This works:
Additional Details
OpenTelemetry Setup Code
No response
package.json
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: