search

open-telemetry / semantic-conventions

Defines standards for generating consistent, accessible telemetry across a variety of domains
Apache License 2.0
256 stars 165 forks source link

Transfer semconv issues from spec repo to this repo? #33

Open tigrannajaryan opened 1 year ago

tigrannajaryan commented 1 year ago

Do we plan to move open semconv issues to this repo?

jsuereth commented 1 year ago

This is still under discussion.

  1. We're deciding if we want to preserve the same labels between them
  2. As seen from otel-proto, we still expect folks to open bugs in the specification repo, so we'll still need to look at it
  3. It's unclear if specification repo issues still need to fix specification components or are PURELY semconv.

We haven't decided one way or the other yet, but it wasn't a clear "yes"

Oberon00 commented 1 year ago

We're deciding if we want to preserve the same labels between them

👍 We may want some non-default labels, but only if there is any benefit (did anyone ever filter for semconv + trace for example?)

It's unclear if specification repo issues still need to fix specification components or are PURELY semconv.

Most open semconv issues should be clearly moved here. There might be a few where it's unclear, but the spec repo has enough open issues as it is, so in doubt I would move to semconv. One could also make this a largish effort and clean out old stale tickets (i.e., close instead of move some/many tickets)

As seen from otel-proto, we still expect folks to open bugs in the specification repo, so we'll still need to look at it

After https://github.com/open-telemetry/opentelemetry-specification/issues/3504 this should hopefully be rare. And then "we'll still need to look at it" is no longer really true, for the few that may still be misdirected, IMHO the spec repo owners are responsible for transferring them (there is a large overlap anyway at the moment between spec and semconv people)