Liudmila Molkova
@neskazu.bsky.social
Software engineer working on observability; member of the OpenTelemetry Technical Committee.
Serving up sarcastic takes on software engineering. Opinions my own.
Serving up sarcastic takes on software engineering. Opinions my own.
Also you can disable receive activities - they are coming from `Azure.Messaging.ServiceBus.ServiceBusReceiver` source and you subscribe in a complicated manner to avoid listening to it. If only .NET OTel gods allowed better filtering when adding a source ;)
January 25, 2025 at 8:06 PM
Also you can disable receive activities - they are coming from `Azure.Messaging.ServiceBus.ServiceBusReceiver` source and you subscribe in a complicated manner to avoid listening to it. If only .NET OTel gods allowed better filtering when adding a source ;)
Can you give me a hint of what's in your hosted service?
Do you use ServicBusReceiver client or ServicBusProcessor?
We should not report them at all when SBProcessor is used.
We should still create them for the processing loop.
Do you use ServicBusReceiver client or ServicBusProcessor?
We should not report them at all when SBProcessor is used.
We should still create them for the processing loop.
January 25, 2025 at 6:40 PM
Can you give me a hint of what's in your hosted service?
Do you use ServicBusReceiver client or ServicBusProcessor?
We should not report them at all when SBProcessor is used.
We should still create them for the processing loop.
Do you use ServicBusReceiver client or ServicBusProcessor?
We should not report them at all when SBProcessor is used.
We should still create them for the processing loop.