Skip to content

Project Tracking: JVM runtime metrics stability #3311

@trask

Description

@trask

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

Spec: JVM runtime metric stability

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.

Metadata

Metadata

Assignees

Labels

area:semantic-conventionsRelated to semantic conventionsspec:metricsRelated to the specification/metrics directory

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions