Declare Trace part of the protocol as Stable about opentelemetry-proto HOT 7 CLOSED

There is also the attributes part which is not fully finalized (no support for arrays as defined in specs), maybe that is the only blocker to declare stable.

from opentelemetry-proto.

#157 is now merged and #150 is discarded.

I went over the entire spec and do not see any other areas of the spec that require changes in the Trace protocol/schema now or in the near future.

I suggest that we therefore declare the Trace part of the protocol Stable. I will prepare a PR for that and we can also discuss in the next Spec SIG meeting.

from opentelemetry-proto.

@open-telemetry/specs-approvers please comment.

from opentelemetry-proto.

We (Shopify) want to start using OTLP throughout our trace collection pipeline. The Beta status is a blocker for us to roll it out in production. We’d very much like to see the Traces part of the protocol declared Stable.

from opentelemetry-proto.

@bogdandrutu yes, you are right. And we need to do that properly to make sure it is consistent in the future with the support for array values that Logs proto also need.
I am going to work on this and will aim to submit proposals for all breaking and anticipated changes as soon as I can.

from opentelemetry-proto.

Currently there are two outstanding breaking changes:
#150 (agreement required, @bogdandrutu I think they're waiting for your opinion on this)
#157 (uncontroversial, will hopefully merge soon, we should certainly include this in the first stable version)

from opentelemetry-proto.

@tigrannajaryan open-telemetry/opentelemetry-specification#376 was re-opened (which is related to one of the mentioned PRs - the nested maps one).

I suggest we hold on a little bit till some discussion happens there (and I suggest attending the SIG call tomorrow, so we could discuss a little bit a few last-time doubts).

from opentelemetry-proto.