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

EventHubs: if received message does not have trace context, spans are not created #25182

Closed
lmolkova opened this issue Nov 3, 2021 · 0 comments · Fixed by #26180
Closed

EventHubs: if received message does not have trace context, spans are not created #25182

lmolkova opened this issue Nov 3, 2021 · 0 comments · Fixed by #26180
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs OpenTelemetry OpenTelemetry instrumentation

Comments

@lmolkova
Copy link
Member

lmolkova commented Nov 3, 2021

Describe the bug
If EventHubs message does not have diagnositc-id in properties, spans are not created

To Reproduce
Send event from non-instrumented producer

Code Snippet
e.g. eventhub spring binder

	@Bean
	public Consumer<Message<String>> consume() {
		return message -> { .. }
        }

Expected behavior
Process span should be created regardless of diagnosticId is present or not (as you might want to monitor consumer even if you don't own or monitor producer)

@lmolkova lmolkova self-assigned this Nov 3, 2021
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 3, 2021
@lmolkova lmolkova added Client This issue points to a problem in the data-plane of the library. Event Hubs OpenTelemetry OpenTelemetry instrumentation and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Nov 3, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs OpenTelemetry OpenTelemetry instrumentation
Projects
None yet
2 participants