Closed trask closed 8 months ago
Hello @tigrannajaryan just checking in. Any update on this one?
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
I'll join the working group again. Thanks!
Please sign me up too. Thank you!
I'm in too! Thanks for thinking of me.
Please count me in. Thanks! Peter Findeisen
From: Trask Stalnaker @.> Sent: Wednesday, April 5, 2023 9:57 AM To: open-telemetry/opentelemetry-specification @.> Cc: Peter Findeisen (pfindeis) @.>; Mention @.> Subject: Re: [open-telemetry/opentelemetry-specification] Project Tracking: JVM runtime metrics stability (Issue #3311)
hi @edburnshttps://github.com/edburns! we are still in the "staffing" phase for this working group / project
poking folks who may be interested...
@brunobathttps://github.com/brunobat @breedx-splkhttps://github.com/breedx-splk @donbournehttps://github.com/donbourne @Emily-Jianghttps://github.com/Emily-Jiang @fstabhttps://github.com/fstab @jackshirazihttps://github.com/jackshirazi @jeanbisuttihttps://github.com/jeanbisutti @jsuerethhttps://github.com/jsuereth @jonatan-ivanovhttps://github.com/jonatan-ivanov @kittylysthttps://github.com/kittylyst @laurithttps://github.com/laurit @mateuszrzeszutekhttps://github.com/mateuszrzeszutek @PeterF778https://github.com/PeterF778 @rapphilhttps://github.com/rapphil @roberttoyonagahttps://github.com/roberttoyonaga @tylerbensonhttps://github.com/tylerbenson @zeitlingerhttps://github.com/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
— Reply to this email directly, view it on GitHubhttps://github.com/open-telemetry/opentelemetry-specification/issues/3311#issuecomment-1497827000, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVXBUCMQVNPOXIDWNBJJHS3W7WP55ANCNFSM6AAAAAAVWUM3O4. You are receiving this because you were mentioned.Message ID: @.***>
Please sign me up too. Thank you!
@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
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).
Please include me as well - thanks.
thank you all for voting!!
results are in, and we will be meeting:
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
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.
Same -- my email address is not registered on CNCF slack. Anyone know how to get an invite to that?
@vijaysun-omr @donbourne you should be able to create an account here: http://slack.cncf.io/, let me know if that works, thx!
Thanks @trask , that worked!
Checking in again on this @trask any update?
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
JVM metrics will be stable with the next semantic convention release, which will hopefully be later this week.
@trask , I think @vijaysun-omr has a minor correction coming later today... about OpenJ9 vs. J9 terms
Yes it is just a minor correction that maybe @trask can just make, "OpenJ9" is the name to use rather than "J9"
sure! I sent https://github.com/open-telemetry/semantic-conventions/pull/611 to address
Closing, JVM runtime metrics semconv is now stable, and OpenTelemetry Java Instrumentation 2.0.0 is released which now emits them!
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
Staffing / Help Wanted
The goal is to follow @tedsuo's proposed Semantic Convention Process.
Required staffing for Stage 1 and 2
Meeting Times
April 17 - May 26 (6 weeks):
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.