[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [microprofile-wg] [BALLOT][MicroProfile Telemetry 1.0] Specification - Release Review - VOTE by 28th November (2 weeks)
|
0 (iJUG)
Why:
As discussed earlier, I have concerns
about having a default behaviour in MP Telemetry for enabling of
OpenTelemetry (Otel), that uses an Otel configuration with
inverted default value. Even this is now in the final version a
stable parameter (thanks Bruno's enduring efforts) and we added a
corresponding (important) note in the spec, I think it is still an
issue we should improve in future versions of the spec, including
a clearer definition of the propagator behaviour (a separate and
independent Otel configuration since 1.14.0 of the Otel spec, as
we are based on 1.13.0 in MP Telemetry 1.0 for now, because of on
other Otel issue, that could not be solved in time for the release
- but today is).
In short, I strongly believe
OpenTelemetry is the future for observability, but it is evolving
fast and not stable in all aspects (especially in telemetry data)
- developing it besides the MP (platform) as stand alone spec
could make sense. At least having new releases short after MP 6.0
is an option too - but having breaking changes in MP Telemetry
while included in the MP (platform) requires a major release for
both resulting in a potential delay for new features or fixes. At
the moment we heavily depend on the Otel release cycle...
But starting now with MP Telemetry 1.0
as a replacement for MP OpenTracing is still good news - hopefully
we can improve it soon, especially regarding metrics and logging.
Best,
Jan
Am 15.11.22 um 00:04 schrieb Emily
Jiang via microprofile-wg:
To approve and ratify the Release Review of
MicroProfile Telemetry 1.0 Specification, the Steering Committee
Representatives vote is requested. Please respond with +1
(positive), 0 (abstain), or -1 (reject). Any feedback that you
can provide to support your vote will be appreciated.
The
MicroProfile
Specification Process requires the Specification Committee
and the Community to provide feedback during the approval
process using the relevant documents:
https://github.com/microprofile/microprofile-wg/issues/180
This ballot will be fourteen days, ending on Monday, November
28th. The ballot requires a Super-majority positive vote of the
Steering Committee members. There is no veto. Community input
and Community votes are welcomed. However, only the votes
delivered by Steering Committee Representatives will be counted.
--
Thank you
Emily
Jiang on behalf of the MicroProfile Steering Committee
_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg
