Skip to content

Add metric requirement level to yaml  #406

@jamesmoessis

Description

@jamesmoessis

This stems from open-telemetry/opentelemetry-specification#2972 and https://github.com/open-telemetry/opentelemetry-specification/pull/3158/files

"The HTTP metrics semantic convention spec should provide clarity "what is considered a compliant implementation", e.g. "an implementation is considered compliant if it has implemented all of the metrics described by this spec"

The work required in build-tools is:

  • Add a field to the metrics semconv yaml (should this also be for traces?)
  • Decide where this will be rendered in markdown (most likely the metrics table makes sense) + write it into the markdown renderer

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is neededmodelModifies the model for signals and attributes used by Weaver.

    Projects

    Status

    Improve YAML Schema

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions