Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] EventDataBatch disables diagnostic properties and plugins

See original GitHub issue

EventDataBatch creates AMQP messages before the event sending process so when using it results the loss of Diagnostic-Id, Correlation-Context and any other properties set through plugins without any feedback.

I understand why EventDataBatch generates AMQP message when TryAdd is called but it would be better to give some warning at such situation.

Issue Analytics

State:
Created 4 years ago
Comments:10 (7 by maintainers)

Top GitHub Comments

2reactions

serkantkaracacommented, Feb 1, 2020

We are going to have a fix in the next release.

1reaction

jsquirecommented, May 8, 2020

There should be no immediate action needed, per Serkant’s comment. Trimming up some tags to discourage the bot from interfering with the tracking and release process.

Top Results From Across the Web

Azure Event Hubs client library for Java - version 5.15.6

An Event Hub producer is a source of telemetry data, diagnostics information, usage logs, or other log data, as part of an embedded...

Azure Event Hubs client library for JavaScript

A consumer group is a view of an entire Event Hub. Consumer groups enable multiple consuming applications to each have a separate view...

azure-eventhub

An EventHubProducerClient is a source of telemetry data, diagnostics information, usage logs, or other log data, as part of an embedded device solution,...

Microsoft.Azure.EventHubs.xml 1.0.0.7

EventData.Properties" />. .NET SDK automatically injects context when sending message to the ServiceBus (if diagnostics is enabled by tracing system).