Summary

The Event Hubs client library is instrumented using the .NET EventSource mechanism for logging. When instrumenting or diagnosing issues with applications that consume the library, it is often helpful to have access to the Event Hubs logs.

Though EventSource instrumentation is a common building block for .NET, many applications choose to make use of other logging frameworks which operate differently. As a result, the approach needed for capturing EventSource-based information is not a well-understood sequence of events and would benefit from illustration.

Because all of the Azure client libraries for .NET are built to the same logging standard, the Azure.Core library offers an AzureEventSourceListener to assist with isolating, capturing, and processing logs from the Azure client libraries. It would be helpful to demonstrate use of the AzureEventSourceListener with the Event Hubs client library to assist those interested in capturing logged information.

Scope of Work

• Create a sample that illustrates use of the AzureEventSourceListener with the Event Hubs client library, capturing and using the Event Hubs logs.

• Ensure that the sample demonstrates filtering the captured information to just that of Event Hubs while discussing that the default is to hook all of the Azure client libraries.

Success Criteria

• The sample odetailed by the scope has been created and integrated with the existing Event Hubs client samples.

• Any refactoring or adjustments required for the sample have been made to infrastructure code.

• The sample is recognized by the existing test suite's smoke test and the tests continue to produce deterministic results and pass reliably.