Skip to content

[connector/signaltometrics]Drop collector service name and namespace from metrics#43150

Merged
songy23 merged 2 commits intoopen-telemetry:mainfrom
lahsivjar:sm-singlewriter
Oct 7, 2025
Merged

[connector/signaltometrics]Drop collector service name and namespace from metrics#43150
songy23 merged 2 commits intoopen-telemetry:mainfrom
lahsivjar:sm-singlewriter

Conversation

@lahsivjar
Copy link
Member

Description

signaltometrics.service.* fields were added to the metrics produced from signaltometrics component to ensure single-writer is obeyed (ref). However, we don't require all the fields to ensure this. Based on the description of service.instance.id it is alone enough to ensure single-writer (ref). The other fields leak information about the service which is not desirable and also unnecessary for our purpose.

Link to tracking issue

Fixes #43148

Testing

Updated in PR

Documentation

Updated

Co-authored-by: Gil Raphaelli <graphaelli@gmail.com>
@ChrsMark ChrsMark added ready to merge Code review completed; ready to merge by maintainers and removed waiting-for-code-owners labels Oct 7, 2025
@songy23 songy23 merged commit 3c7140f into open-telemetry:main Oct 7, 2025
213 of 214 checks passed
@github-actions github-actions bot added this to the next release milestone Oct 7, 2025
@lahsivjar lahsivjar deleted the sm-singlewriter branch October 7, 2025 12:36
etserend pushed a commit to etserend/opentelemetry-collector-contrib that referenced this pull request Oct 9, 2025
…from metrics (open-telemetry#43150)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

`signaltometrics.service.*` fields were added to the metrics produced
from signaltometrics component to ensure single-writer is obeyed
([ref](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/signaltometricsconnector#single-writer)).
However, we don't require all the fields to ensure this. Based on the
description of `service.instance.id` it is alone enough to ensure
single-writer
([ref](https://opentelemetry.io/docs/specs/semconv/registry/attributes/service/)).
The other fields leak information about the service which is not
desirable and also unnecessary for our purpose.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#43148

<!--Describe what testing was performed and which tests were added.-->
#### Testing
Updated in PR

<!--Describe the documentation added.-->
#### Documentation
Updated

<!--Please delete paragraphs that you did not use before submitting.-->

---------

Co-authored-by: Gil Raphaelli <graphaelli@gmail.com>
mashhurs pushed a commit to mashhurs/opentelemetry-collector-contrib that referenced this pull request Oct 9, 2025
…from metrics (open-telemetry#43150)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

`signaltometrics.service.*` fields were added to the metrics produced
from signaltometrics component to ensure single-writer is obeyed
([ref](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/signaltometricsconnector#single-writer)).
However, we don't require all the fields to ensure this. Based on the
description of `service.instance.id` it is alone enough to ensure
single-writer
([ref](https://opentelemetry.io/docs/specs/semconv/registry/attributes/service/)).
The other fields leak information about the service which is not
desirable and also unnecessary for our purpose.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#43148

<!--Describe what testing was performed and which tests were added.-->
#### Testing
Updated in PR

<!--Describe the documentation added.-->
#### Documentation
Updated

<!--Please delete paragraphs that you did not use before submitting.-->

---------

Co-authored-by: Gil Raphaelli <graphaelli@gmail.com>
tommyers-elastic pushed a commit to tommyers-elastic/opentelemetry-collector-contrib that referenced this pull request Oct 10, 2025
…from metrics (open-telemetry#43150)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

`signaltometrics.service.*` fields were added to the metrics produced
from signaltometrics component to ensure single-writer is obeyed
([ref](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/signaltometricsconnector#single-writer)).
However, we don't require all the fields to ensure this. Based on the
description of `service.instance.id` it is alone enough to ensure
single-writer
([ref](https://opentelemetry.io/docs/specs/semconv/registry/attributes/service/)).
The other fields leak information about the service which is not
desirable and also unnecessary for our purpose.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
open-telemetry#43148

<!--Describe what testing was performed and which tests were added.-->
#### Testing
Updated in PR

<!--Describe the documentation added.-->
#### Documentation
Updated

<!--Please delete paragraphs that you did not use before submitting.-->

---------

Co-authored-by: Gil Raphaelli <graphaelli@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

connector/signaltometrics ready to merge Code review completed; ready to merge by maintainers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[connector/signaltometrics] signaltometrics.service.{name, namespace} leak unnecessary information for the metrics produced from the component

7 participants