Conversation
Pull request dashboard statusWaiting on the author · refreshed 2026-09-21 21:24 UTC Respond to 1 review item (e.g. link a commit, explain why not, ask a follow-up):
Status above doesn't look right?
|
cc9853d to
c408da2
Compare
Shriprasad-P
left a comment
There was a problem hiding this comment.
Thanks for the PR. Approach looks sensible — please confirm edge cases and failure paths are covered by tests.
e9e6ae6 to
fb426c2
Compare
dcbf560 to
c31187b
Compare
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Explicit detector ordering and fork-time resource refresh can still overwrite configured IDs, and direct user/environment precedence lacks coverage.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 2
Open (3)
What changed in this PR
This PR adjusts resource detector ordering to prevent generated service.instance.id values from overriding configured detector values.
Changes:
- Prepends the service-instance detector.
- Adds detector regression tests.
- Adds a changelog entry.
| File | Description |
|---|---|
opentelemetry-sdk/src/opentelemetry/sdk/resources/__init__.py |
Changes detector ordering. |
opentelemetry-sdk/tests/resources/test_resources.py |
Adds service-instance regression tests. |
.changelog/5660.fixed |
Documents the fix. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…from the user provided values from the resource detectors
29d6592 to
d1c2dc2
Compare


Description
Prevent
ServiceInstanceIdResourceDetectorfrom overwriting an existingservice.instance.idset by another resource detector(ex. Azure) or user configuration. Add regression coverage for detector-, initial-resource-, and environment-provided IDs, while retaining UUID generation when no ID is present.Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Does This PR Require a Contrib Repo Change?
Checklist: