-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[exporter/clickhouse] Add instrumentation scope to span attribute #17408
Comments
/label exporter/clickhouse |
Pinging code owners for exporter/clickhouse: @hanjm @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
looks good. I think store it to resource attribute is reasonable. |
Hi @Frapschen, we are storing traces in Clickhouse to build our custom monitoring dashboards and this library info will help us filter data better. For example, we can find out the slowest libraries, the most frequently used libraries |
got it,I agree with @hanjm, I will add this to my work list. I notice that the clickhouse log exporter also have same issue, I will create new issue and fix it. |
Thank you guys ❤️ |
@huynhtehoa @Frapschen Please see the spec translation guidelines https://github.com/open-telemetry/opentelemetry-specification/blob/7116e72cff72a825bbb83e103c2756706d3106ee/specification/common/mapping-to-non-otlp.md#instrumentationscope . They should be mapped to |
got it |
Component(s)
exporter/clickhouse
Is your feature request related to a problem? Please describe.
Currently, attributes such as
otel.library.name
,otel.library.version
are not added to span attributes. Those attributes are parts ofInstrumentationScope
, which is provided by opentelemetry https://opentelemetry.io/docs/reference/specification/logs/data-model/#field-instrumentationscopeDescribe the solution you'd like
It would be nice to include
otel.library.name
andotel.library.version
in span attributesDescribe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: