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

spec matrix: remove duplicate mention of meter+scope association #3822

Closed

Conversation

tsloughter
Copy link
Member

Fixes duplicate mentions of associating an InstrumentationScope with a Meter in the spec matrix.

Like with the Traces section there is already an entry for:

Associate Meter with InstrumentationScope.

At first I was just removing the line mentioning InstrumentationLibrary but then realized I think this is just a duplicate of what is already listed in the matrix. The removed text is more descriptive than simply saying "associate" but matches the Traces section so I kept that one.

@tsloughter tsloughter requested review from a team January 13, 2024 12:00
@@ -161,8 +161,6 @@ formats is required. Implementing more than one format is optional.
| All methods of any instrument are safe to be called concurrently. | | + | + | + | - | | | | | + | + | |
| `MeterProvider` allows a `Resource` to be specified. | | + | + | + | + | | | + | + | + | + | |
| A specified `Resource` can be associated with all the produced metrics from any `Meter` from the `MeterProvider`. | | + | + | + | + | | | + | + | + | + | |
| The supplied `name`, `version` and `schema_url` arguments passed to the `MeterProvider` are used to create an `InstrumentationLibrary` instance stored in the `Meter`. | | + | - | | + | | | | + | + | - | |
| The supplied `name`, `version` and `schema_url` arguments passed to the `MeterProvider` are used to create an `InstrumentationScope` instance stored in the `Meter`. | | | + | + | | | | + | + | + | | |
Copy link
Member

Choose a reason for hiding this comment

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

Line 108 and this line were introduced by #2276

From I see the intent was to make it clear we want to replace Library by Scope and wanted to have a separate line item to track that the change is done by language implementations.

I am fine with eliminating the duplication and keeping just one line instead of 3, but we need to confirm that indeed the work of renaming Library to Scope is done by ALL languages, otherwise we will loose this particular compatibility nuance.

Can you confirm this with all languages where the 3 lines do not match exactly?

Copy link
Member Author

Choose a reason for hiding this comment

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

Will do.

Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Jan 25, 2024
Copy link

github-actions bot commented Feb 2, 2024

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions bot closed this Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants