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

Remove label mapping for service.instance.id #3497

Merged
merged 14 commits into from
Dec 10, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update .chloggen/service-instanc-id-mapping.yaml
Co-authored-by: Jacob Aronoff <jaronoff97@users.noreply.github.com>
  • Loading branch information
zeitlinger and jaronoff97 authored Nov 28, 2024
commit 68a1b9f975fa9b1f4caea29165f656815877af0a
2 changes: 1 addition & 1 deletion .chloggen/service-instanc-id-mapping.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ issues: [3495]
subtext: |
Technically, this is a breaking change, but we regard it as a bug fix because the previous behavior was incorrect.

In you did have multiple containers and use `app.kubernetes.io/instance` to set the `service.instance.id`,
if you did have multiple container instrumentation and use `app.kubernetes.io/instance` to set the `service.instance.id`,
you will now see multiple instances in the UI - which is the correct behavior.

You can still use the attribute `resource.opentelemetry.io/service.instance.id` to set the `service.instance.id`,
Expand Down
Loading