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

Project Tracking: JVM runtime metrics stability #3311

Closed
trask opened this issue Mar 10, 2023 · 22 comments
Closed

Project Tracking: JVM runtime metrics stability #3311

trask opened this issue Mar 10, 2023 · 22 comments
Assignees
Labels
area:semantic-conventions Related to semantic conventions spec:metrics Related to the specification/metrics directory

Comments

@trask
Copy link
Member

trask commented Mar 10, 2023

Description

The OpenTelemetry Java community would like to stabilize JVM runtime metrics in order to help native adoption of the OTel Metrics API among key Java frameworks such as MicroProfile.

Project Board

https://github.com/orgs/open-telemetry/projects/49

Deliverables

  • Mark the JVM runtime metrics as stable.
  • Update existing OpenTelemetry JVM runtime metrics instrumentation to conform with the stable conventions.

Staffing / Help Wanted

The goal is to follow @tedsuo's proposed Semantic Convention Process.

  • Stage 1: Working Group Preparation
  • Stage 2: Stabilizing the Specification
  • Stage 3: Implementation (we expect this to be a very short or non-existent)

Required staffing for Stage 1 and 2

Meeting Times

April 17 - May 26 (6 weeks):

  • Tuesdays 10:00-10:30 Pacific Time
  • Thursdays 9:00-10:00 Pacific Time (this is the regular weekly Java meeting)
  • Fridays 8:30-9:00 Pacific Time

Timeline

Stage 1 (Working Group Preparation) is happening now.

Stage 2 (Stabilizing the Specification) will begin as soon as we have adequate staffing for this project, and we coordinate a weekly meeting times (currently targeting mid-april).

Stage 3 (Implementation) will begin as soon as the JVM runtime metrics are marked stable, and it should be relatively short since we only need to update conformance to the specification for a single language.

Labels

The tracking issue should be properly labeled to indicate what parts of the specification it is focused on.

Linked Issues and PRs

All PRs, Issues, and OTEPs related to the project should link back to the tracking issue, so that they can be easily found.

@trask trask added area:semantic-conventions Related to semantic conventions spec:metrics Related to the specification/metrics directory labels Mar 10, 2023
@trask trask assigned trask and unassigned tigrannajaryan Mar 10, 2023
@edburns
Copy link

edburns commented Apr 5, 2023

Hello @tigrannajaryan just checking in. Any update on this one?

@trask
Copy link
Member Author

trask commented Apr 5, 2023

hi @edburns! we are still in the "staffing" phase for this working group / project

poking folks who may be interested...

@brunobat @breedx-splk @donbourne @Emily-Jiang @fstab @jackshirazi @jeanbisutti @jsuereth @jonatan-ivanov @kittylyst @laurit @mateuszrzeszutek @PeterF778 @rapphil @roberttoyonaga @tylerbenson @zeitlinger

please ping back on this issue this week, I will send out a meeting time poll next week for folks who would like to participate

@breedx-splk
Copy link
Contributor

I'll join the working group again. Thanks!

@jonatan-ivanov
Copy link
Member

Please sign me up too. Thank you!

@kittylyst
Copy link

I'm in too! Thanks for thinking of me.

@PeterF778
Copy link

PeterF778 commented Apr 10, 2023 via email

@fstab
Copy link
Member

fstab commented Apr 10, 2023

Please sign me up too. Thank you!

@trask
Copy link
Member Author

trask commented Apr 11, 2023

@jack-berg @breedx-splk @jonatan-ivanov @kittylyst @PeterF778 @fstab (and anyone else who still wants to join!) please add your availability to https://strawpoll.com/polls/jVyG8xKxYn7

the goal is to schedule two 30-minute meetings a week for 6 weeks, starting next week.

we'll set aside some time in the weekly Thu Java meeting to touch base on this work also.

@open-telemetry/technical-committee since this is a language-specific working group, I'm comfortable moving forward with only one Technical Committee member (@jack-berg)

@Emily-Jiang @donbourne it would be great if someone from MicroProfile is able to join this working group

@donbourne
Copy link

Please include me - I can help provide MicroProfile and app server perspective. Also I've invited my colleague, @vijaysun-omr , to join (with extensive Java performance experience).

@zeitlinger
Copy link
Member

Please include me as well - thanks.

@trask
Copy link
Member Author

trask commented Apr 13, 2023

thank you all for voting!!

results are in, and we will be meeting:

  • Tuesdays 10:00-10:30 Pacific Time
  • Thursdays 9:00-10:00 Pacific Time (this is the regular weekly Java meeting)
  • Fridays 8:30-9:00 Pacific Time

for the next 6 weeks.

the google calendar is updated with these meetings: https://calendar.google.com/calendar?cid=Z29vZ2xlLmNvbV9iNzllM2U5MGo3YmJzYTJuMnA1YW41bGY2MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t

and you can subscribe to the google calendar invites by joining this google group https://groups.google.com/g/opentelemetry-calendar-java

we will use the #otel-java #otel-jvm-runtime-stability-wg slack channel for async discussions

@vijaysun-omr
Copy link

My email address is not registered on the CNCF slack it seems, and so I cannot join the slack channel that was mentioned on today's call at the moment.

@donbourne
Copy link

Same -- my email address is not registered on CNCF slack. Anyone know how to get an invite to that?

@trask
Copy link
Member Author

trask commented Apr 18, 2023

@vijaysun-omr @donbourne you should be able to create an account here: http://slack.cncf.io/, let me know if that works, thx!

@donbourne
Copy link

Thanks @trask , that worked!

@edburns
Copy link

edburns commented Oct 2, 2023

Checking in again on this @trask any update?

@trask
Copy link
Member Author

trask commented Nov 10, 2023

hi @edburns, sorry for the late reply! we just released the very first stable semantic convention (HTTP).

the Java SIG discussed the JVM semconv stability timeline yesterday, and we are going to see if we can finish this effort in time for our mid-December Java release

@trask
Copy link
Member Author

trask commented Dec 12, 2023

JVM metrics will be stable with the next semantic convention release, which will hopefully be later this week.

@donbourne
Copy link

@trask , I think @vijaysun-omr has a minor correction coming later today... about OpenJ9 vs. J9 terms

@vijaysun-omr
Copy link

Yes it is just a minor correction that maybe @trask can just make, "OpenJ9" is the name to use rather than "J9"

@trask
Copy link
Member Author

trask commented Dec 14, 2023

sure! I sent open-telemetry/semantic-conventions#611 to address

@trask
Copy link
Member Author

trask commented Jan 25, 2024

Closing, JVM runtime metrics semconv is now stable, and OpenTelemetry Java Instrumentation 2.0.0 is released which now emits them!

@trask trask closed this as completed Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:semantic-conventions Related to semantic conventions spec:metrics Related to the specification/metrics directory
Projects
None yet
Development

No branches or pull requests