Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telemetry attribute service.name doesn't get sent correctly #1007

Closed
vordimous opened this issue May 7, 2024 · 1 comment · Fixed by #1048
Closed

Telemetry attribute service.name doesn't get sent correctly #1007

vordimous opened this issue May 7, 2024 · 1 comment · Fixed by #1048
Assignees
Labels
bug Something isn't working

Comments

@vordimous
Copy link
Contributor

Describe the bug
Setting the service.namespace and service.name attributes don't show up in with those names in the exporters.

To Reproduce
Steps to reproduce the behavior:

  1. Run the aklivity/opentelemetry-demo using the docker compose deployment.
  2. wait for everything to start.
  3. Fetch the orders from the Kafka topic: curl http://localhost:7114/orders
  4. See Zilla metrics in Grafana Explorer
  5. the configured service.name shows up as job
  6. when both service.namespace and service.name are configured they are joined with a /

Expected behavior
Configuring the service.name should show up as service_name on all of the metrics and logs.

Additional context

@vordimous vordimous added the bug Something isn't working label May 7, 2024
@vordimous
Copy link
Contributor Author

I was able to do some more tweaks to get the metrics to have a consistent job attribute by configuring just the telemetry attributes service.name without a service.namespace. I could then clone the demo dashboard and tell it to use the job label instead of the service_name label when filtering metrics and logs to show zilla logs and metrics along with the other services.

This issue still needs to be addressed based on how other OTEL SDKs export a service name and determine why we can use service.name and service.namespace to manipulate the job label and if that is the intended functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants