Skip to content

Have InstrumentationScope use normative language#4488

Merged
carlosalberto merged 23 commits intoopen-telemetry:mainfrom
carlosalberto:normative-instr-scope
Jun 6, 2025
Merged

Have InstrumentationScope use normative language#4488
carlosalberto merged 23 commits intoopen-telemetry:mainfrom
carlosalberto:normative-instr-scope

Conversation

@carlosalberto
Copy link
Contributor

@carlosalberto carlosalberto commented Apr 25, 2025

Fixes #4450

Moved the InstrumentationScope definition from glossary into common/instrumentation-scope.md, and massaged it using normative language, including some examples. Also removed the compile-time concept restriction (as clarified in the related issue, this limitation does not exist in a few SIGs).

This also means moving its definition from glossary
into the actual specification (common/).
@carlosalberto carlosalberto force-pushed the normative-instr-scope branch from 289dd11 to 462ae99 Compare April 28, 2025 16:15
@carlosalberto carlosalberto force-pushed the normative-instr-scope branch from 462ae99 to c84fa83 Compare April 29, 2025 14:15
@carlosalberto carlosalberto marked this pull request as ready for review April 29, 2025 14:29
@carlosalberto carlosalberto requested review from a team April 29, 2025 14:29
@carlosalberto
Copy link
Contributor Author

Moved the InstrumentationScope section into its own file, and added some examples. Please review them @lmolkova @jade-guiton-dd

Copy link
Contributor

@jsuereth jsuereth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed this is needed, and it's a good improvement.

Lots of questions / nits - nothing blocking.

@carlosalberto carlosalberto force-pushed the normative-instr-scope branch from 472f79d to 5872000 Compare May 9, 2025 00:40
@carlosalberto
Copy link
Contributor Author

@jade-guiton-dd @jsuereth Used "software unit" instead of either "code" or "application". That should keep it general/abstract enough IMHO.

carlosalberto and others added 2 commits May 15, 2025 16:24
Co-authored-by: Robert Pająk <pellared@hotmail.com>
Co-authored-by: Nathan L Smith <nathan.smith@elastic.co>
@carlosalberto carlosalberto force-pushed the normative-instr-scope branch from 770021f to 5c71c39 Compare May 23, 2025 14:56
@carlosalberto
Copy link
Contributor Author

@MrAlias Please review.

@carlosalberto
Copy link
Contributor Author

@MrAlias I think this is good enough and I'd like to merge this in the following days as I do think your feedback has been addressed. Let me know otherwise.

@carlosalberto carlosalberto added this pull request to the merge queue Jun 6, 2025
Merged via the queue into open-telemetry:main with commit 9736aa2 Jun 6, 2025
10 of 11 checks passed
@carlosalberto carlosalberto deleted the normative-instr-scope branch June 6, 2025 14:12
@@ -0,0 +1,52 @@
<!--- Hugo front matter used to generate the website version of this page:
linkTitle: Instrumentation Scope
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't include a linkTitle if it is the same as the time.

chalin added a commit to open-telemetry/opentelemetry.io that referenced this pull request Jun 10, 2025
chalin added a commit to open-telemetry/opentelemetry.io that referenced this pull request Jun 10, 2025
chalin added a commit to open-telemetry/opentelemetry.io that referenced this pull request Jun 11, 2025
github-merge-queue bot pushed a commit that referenced this pull request Jun 12, 2025
### Metrics

- Prometheus receiver can expect `otel_scope_schema_url` and
`otel_scope_[attribute]` labels on all metrics.

([#4505](#4505))
- Prometheus receiver no longer expects `otel_scope_info` metric.

([#4505](#4505))
- Prometheus exporter adds `otel_scope_schema_url` and
`otel_scope_[attribute]` labels on all metrics.

([#4505](#4505))
- Prometheus exporter no longer exports `otel_scope_info` metric.

([#4505](#4505))

### Entities

- Define rules for setting identifying attributes.

([#4498](#4498))
- Define rules for entity-resource referencing model.

([#4499](#4499))

### Common

- Move Instrumentation Scope definition from glossary to a dedicated
document and use normative language.

([#4488](#4488))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Endorse use of runtime-defined instrumentation scope attributes