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.

Sign up for GitHub

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

Jump to bottom

Stabilize Metrics Instrument Enabled #4215

Open
codeboten opened this issue Sep 18, 2024 · 8 comments
Open

Stabilize Metrics Instrument Enabled #4215

codeboten opened this issue Sep 18, 2024 · 8 comments
Labels
spec:metrics Related to the specification/metrics directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted

Comments

@codeboten
Copy link
Contributor

I believe the last issue around stabilizing the Enabled API for metric instruments was #4211 and it is now merge.

Are there other issues preventing this from stabilizing?
@codeboten codeboten added the spec:metrics Related to the specification/metrics directory label Sep 18, 2024
@sfc-gh-bdrutu
Copy link

I support this.

@jack-berg
Copy link
Member

Do we meet the requirement for prototype implementations?

Java has a prototype. What other languages have prototypes?

@codeboten
Copy link
Contributor Author

Go has a prototype in this PR open-telemetry/opentelemetry-go#5768

codeboten added a commit to codeboten/opentelemetry-specification that referenced this issue Sep 19, 2024
@codeboten
Mark Enabled API for synchronous instruments stable
79af5d1 
This marks the API stable.

Fixes open-telemetry#4215

Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
@codeboten
Copy link
Contributor Author

@cijothomas pointed out that .net already supports this API https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.metrics.instrument.enabled?view=net-8.0

@codeboten codeboten mentioned this issue Sep 19, 2024
Closed
4 tasks
@svrnm svrnm added the triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted label Sep 30, 2024
@svrnm
Copy link
Member

svrnm commented Sep 30, 2024

how many prototypes do we need?

@reyang
Copy link
Member

reyang commented Oct 9, 2024

how many prototypes do we need?

Three.

@jack-berg
Copy link
Member

Go has a prototype in this PR open-telemetry/opentelemetry-go#5768

Discussed in the 10/9/2024 TC meeting. A PR doesn't count as a prototype. For user facing APIs, part of the point of prototyping is to get in the hands of users to solicit feedback / issues, and a PR doesn't accomplish this goal. Several languages have invested in tooling to be able to differentiate between experimental and stable APIs. We recommend that languages develop this tooling. Now that the spec has stable traces, metrics, and logs, the continued evolution of these signals is dependent on prototyping and tooling to publish prototypes separately from stable APIs.

@pellared
Copy link
Member

I created a blocking issue:

@github-actions github-actions bot added the triage:followup Needs follow up during triage label Oct 15, 2024
@pellared pellared mentioned this issue Oct 15, 2024
Draft
@trask trask removed the triage:followup Needs follow up during triage label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
spec:metrics Related to the specification/metrics directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Mark Enabled API for synchronous instruments stable codeboten/opentelemetry-specification
7 participants
@trask @codeboten @svrnm @pellared @reyang @jack-berg @sfc-gh-bdrutu