Skip to content
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 messaging.consumer_id to span attribute for Kafka Consumer #1332

Merged
merged 1 commit into from
Aug 15, 2021

Conversation

kenfinnigan
Copy link
Collaborator

I wanted to do the same for AMQP, but I couldn't find where I can get the Client ID from.

If someone knows, I can add to this PR

@kenfinnigan kenfinnigan added this to the 3.9.0 milestone Jul 27, 2021
@Ladicek
Copy link
Collaborator

Ladicek commented Jul 28, 2021

I assume this is related to open-telemetry/opentelemetry-specification#1810 ? Would be good to have it in a comment.

As for AMQP, I don't know what AMQP concept would be a good fit. Perhaps the container ID, but it seems we set that to null if the user doesn't configure it, so it's probably almost always empty.

@Ladicek
Copy link
Collaborator

Ladicek commented Jul 28, 2021

One thing we could add relatively easily for AMQP is a correlation ID, though :-)

@kenfinnigan
Copy link
Collaborator Author

Yes, that's the spec change to add consumer_id.

I thought there was an AMQP Client Id, but maybe I was wrong

@cescoffier cescoffier merged commit 840f347 into smallrye:main Aug 15, 2021
@kenfinnigan kenfinnigan deleted the otel-consumer-id branch September 3, 2021 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants