-
Notifications
You must be signed in to change notification settings - Fork 821
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
Example and tests for otel collector exporter is not updated still uses serviceName
#2278
Comments
In the updated example just a heads up import { ResourceAttributes } from '@opentelemetry/semantic-conventions'
import { Resource } from '@opentelemetry/resources' both libraries also are still on 0.20.0 |
Thanks @delaneyj 🙏 |
The first one was allowed because of the The second one was allowed because examples aren't type checked. |
Can we remove the any then? Ohhh I see how can we enable type checking in the examples do we add some github actions |
The examples aren't written in typescript. in order to enable type checking, they would need to be modified for it. This is something we've talked about in the past but just haven't gotten to |
Sure do you want to make a PR? |
The opentelemetry collector exporter is not updated. In examples and tests, It still uses
serviceName
for config and looking at the codebase it does not expose that anymore.I wonder how these got in if we use typescript
opentelemetry-js/packages/opentelemetry-exporter-collector/test/node/CollectorTraceExporter.test.ts
Line 61 in a3b7738
opentelemetry-js/examples/collector-exporter-node/tracing.js
Line 15 in a3b7738
I am also unsure what should be the practice now? Should this be how we configure serviceName now?
#2271
The text was updated successfully, but these errors were encountered: