Top opentelemetry-specification issues

RecordException and Span.Status

api error-reporting p2 allowed-for-ga trace
iNikem picture iNikem·25 Sep 2020·10 Comments

Proposal: Define semantic conventions in JSON/YAML

semantic-conventions enhancement p2 required-for-ga
bogdandrutu picture bogdandrutu·4 Apr 2020·9 Comments
👍9

Define the metrics that we expect to capture from RPC integrations

semantic-conventions p2 required-for-ga metrics
mtwo picture mtwo·20 Mar 2020·5 Comments
👍2

[meta] Do not "Require branches to be up to date before merging" in the repository settings

Oberon00 picture Oberon00·11 Mar 2020·8 Comments
👍6

Change the spec to be closer to OpenTracing

rochdev picture rochdev·9 Jul 2019·6 Comments

Define the list of standard exporters that SDK should support

sdk needs discussion
bogdandrutu picture bogdandrutu·13 May 2019·6 Comments

Distinction between structured `Body` and `Attributes`

help wanted logs
jmm picture jmm·13 Apr 2021·12 Comments

Open Telemetry SDK should not be required when instrumenting a Library

api metrics
victlu picture victlu·11 Feb 2021·16 Comments

Consider making faas.id a span attribute instead of a resource attribute

semantic-conventions after-ga resource
mateuszrzeszutek picture mateuszrzeszutek·26 Nov 2020·15 Comments
👍1

Rename "Label" concept to "Attribute" for consistency with OpenTelemetry tracing

data-model p1 required-for-ga metrics
jmacd picture jmacd·19 Oct 2020·11 Comments
👍6
 Previous issues
Next issues