-
Notifications
You must be signed in to change notification settings - Fork 3.1k
setting TraceID and SpanID fields in Exemplar objects in spanmetricsp… #13401
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
setting TraceID and SpanID fields in Exemplar objects in spanmetricsp… #13401
Conversation
Do we need to create a new issue for this so that it can be added to unreleased yaml? I couldn't find an existing issue that states this exact problem but there are a few exemplar related issues that are generally related, not sure if I could use on of those. Or would this be a "chore" item that can skip the change log check. |
If no issue, you can use the PR number as the issue number in the unreleased template. |
31a6c90
to
925b749
Compare
91e0ce8
to
b49111d
Compare
@bogdandrutu pinging for review :) |
826fa33
to
d49c57f
Compare
@bogdandrutu pinging for review :) |
Currently TraceID and SpanID fields of Examplar are set in
FilteredAttributes
(here) inspanmetricsprocessor
and passed around but these fields are not part ofFilteredAttributes
as per the data model: https://pkg.go.dev/go.opentelemetry.io/collector/pdata/internal/data/protogen/metrics/v1#Exemplarspanmetricsprocessor
prometheusexporter
is updated to use TraceID, SpanID fields inExemplar
.Testing:
Unit tests are updated to test TraceID and SpanID fields instead of checking for those in
FilteredAttributes