Skip to content

[FEATURE REQ] EventHubs consumer is not traced #28552

Description

@lmolkova

EventHubConsumerClient (sync and async) receive calls are not instrumented and tracing is not supported. In case a customer does not use the processor, it makes receiving messages untraceable.

Consumer needs to be instrumented

  • it should contain links to received messages (which needs a delayed span start)
  • we should investigate the ability to allow extracting context from EventHub messages so customers who don't use Processor could also trace message processing manually. As a bare minimum, we should provide code samples to achieve it

Metadata

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Event HubsOpenTelemetryOpenTelemetry instrumentation

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions