[FEATURE REQ] Document ActivitySource names or naming conventions

[lmolkova]

Library name

All

Please describe the feature.

Users sometimes what to enable specific ActivitySources and exclude others. We only document Azure.* and don't give any guidance on source names beyond that.

E.g. storage one is Azure.Storage, appconfig one is Azure.Data.AppConfiguration and eventhubs is Azure.Messaging.EventHubs.

In some cases, they are defined explicitly (EventHubs), but in most cases, the name corresponds to the namespace in which derived ClientOptions are defined.

The convention: <packageName>.<className>.

E.g. ServiceBus should have the following sources

• Azure.Messaging.ServiceBus.ServiceBusReceiver
• Azure.Messaging.ServiceBus.Message
• Azure.Messaging.ServiceBus.ServiceBusSender
• Azure.Messaging.ServiceBus.ServiceBusProcessor

It's recommended to enable Azure SDK tracing in one of the following ways:

• AddSource("Azure.*) - all activities
• AddSource("<packageName>.*)
  • all activities from specific library such as Azure.Messaging.ServiceBus
  • no activities for HTTP requests (they are coming from Azure.Core.Http and need to be enabled additionally)
• AddSource("<packageName>.<clientName>") - activities from individual clients (e.g. when Azure.Messaging.ServiceBus.ServiceBusProcessor is used, receiver activities won't be reported)