You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the ActivitySource best practices, each library or library subcomponent can, and often should, create its own source. However, when this is done, the exporter (Zipkin, for example) creates an attribute named otel.library.name with the value set to the ActivitySource.Name. If there is only a single ActivitySource with the same name as the library, this is not a problem. However, if an ActivitySource is created for multiple types in the library, the attribute will show the incorrect name of the library.
What is the recommendation for naming ActivitySource. Use one and name it the same as the library?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As per the ActivitySource best practices, each library or library subcomponent can, and often should, create its own source. However, when this is done, the exporter (Zipkin, for example) creates an attribute named otel.library.name with the value set to the ActivitySource.Name. If there is only a single ActivitySource with the same name as the library, this is not a problem. However, if an ActivitySource is created for multiple types in the library, the attribute will show the incorrect name of the library.
What is the recommendation for naming ActivitySource. Use one and name it the same as the library?
Beta Was this translation helpful? Give feedback.
All reactions