Skip to content
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.

application to ocagent to jaeger exporter loose service name #568

Open
daeMOn63 opened this issue Jun 10, 2019 · 2 comments
Open

application to ocagent to jaeger exporter loose service name #568

daeMOn63 opened this issue Jun 10, 2019 · 2 comments

Comments

@daeMOn63
Copy link

I have an application registering an ocagent exporter like so:

oce, err := ocagent.NewExporter(
		ocagent.WithInsecure(),
		ocagent.WithServiceName("my-app")
)

And this ocagent configuration:

receivers:
  opencensus:
    address: "0.0.0.0:55678"

exporters:
  jaeger:
    collector_endpoint: "http://jaeger:14268/api/traces"

When browsing to the jaeger interface, I'm expecting to see the service "my-app" being listed, but instead, I only have a default "Opencensus" service.

I managed to change the default service name by adding the service_name to the jaeger configuration:

receivers:
  opencensus:
    address: "0.0.0.0:55678"

exporters:
  jaeger:
    service_name: "my-app"
    collector_endpoint: "http://jaeger:14268/api/traces"

But I would prefer not having to do that, so I could have multiple applications exporting to the same agent, and still the jaeger UI display the service names as specified in the application.

Is there any way to achieve this ?

@pjanotti
Copy link

Hi @daeMOn63, unfortunately this is a current issue with the exporters, please take a look at #551 (comment) and see if you can use that workaround. Notice that the collector configured with smallish queues will have a footprint similar to the agent.

@pjanotti
Copy link

Instance of #198

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants