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
Setting the service.name on the telemetry settings for the Collector has no effect, and traces generated by the Collector have no service name attacked (not even a default one). Internal metrics are handling this correctly.
Describe the bug
Setting the
service.name
on the telemetry settings for the Collector has no effect, and traces generated by the Collector have no service name attacked (not even a default one). Internal metrics are handling this correctly.Steps to reproduce
What did you expect to see?
On a second Collector on port 5317, I would expect to see this on the traces received:
What did you see instead?
What version did you use?
0.103.1
The text was updated successfully, but these errors were encountered: