Skip to content

Issues: open-telemetry/opentelemetry-specification

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
53 Open 281 Closed
53 Open 281 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

SeverityNumber as required parameter in EmitEvent area:api Cross language API specification issue sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4261 opened Oct 15, 2024 by pellared
2
Should span Status description be of low cardinality? area:api Cross language API specification issue area:semantic-conventions Related to semantic conventions spec:trace Related to the specification/trace directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3687 opened Sep 9, 2023 by jcarres-mdsol
6
Advice/hint APIs should be applied to all signals (when applicable) area:api Cross language API specification issue area:configuration Related to configuring the SDK spec:metrics Related to the specification/metrics directory spec:trace Related to the specification/trace directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#3557 opened Jun 16, 2023 by lmolkova
1
Add a count argument to histogram record API area:api Cross language API specification issue spec:metrics Related to the specification/metrics directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#3369 opened Apr 4, 2023 by jack-berg
9
Global MeterProvider Get/Set API is under-defined area:api Cross language API specification issue spec:metrics Related to the specification/metrics directory
#3068 opened Jan 4, 2023 by MrAlias
@yurishkuro
10
Add ability to *reset* metrics to 0 in UpDownCounter area:api Cross language API specification issue area:semantic-conventions Related to semantic conventions semconv:database spec:metrics Related to the specification/metrics directory
#3037 opened Dec 15, 2022 by haddasbronfman
@carlosalberto
6
Clarify what happens if attributes are mutated after calling APIs area:api Cross language API specification issue spec:miscellaneous For issues that don't match any other spec label
#2592 opened May 31, 2022 by tigrannajaryan
@yurishkuro
semconv: add rpc.type and rpc.status area:api Cross language API specification issue area:semantic-conventions Related to semantic conventions question Question for discussion spec:metrics Related to the specification/metrics directory
#2419 opened Mar 16, 2022 by 1046102779
@arminru
5
provide optional access to root span area:api Cross language API specification issue spec:trace Related to the specification/trace directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#2109 opened Nov 5, 2021 by brettmc
11
the operation of attributes not defined area:api Cross language API specification issue question Question for discussion spec:miscellaneous For issues that don't match any other spec label
#1857 opened Aug 9, 2021 by ddzrc
@bogdandrutu
8
Return type of callback functions for Asynchronous Instruments area:api Cross language API specification issue release:after-ga Not required before GA release, and not going to work on before GA spec:metrics Related to the specification/metrics directory
#1732 opened May 28, 2021 by jonatan-ivanov
2
Allow supplying a callback for adding new attributes when spans start area:api Cross language API specification issue enhancement New feature or request spec:trace Related to the specification/trace directory
#1724 opened May 26, 2021 by zionsofer
16
PassThroughTextMapPropagator area:api Cross language API specification issue spec:context Related to the specification/context directory spec:trace Related to the specification/trace directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#1717 opened May 21, 2021 by anuraaga
7
Does OpenTelemetry need "enum" metric type? area:api Cross language API specification issue area:data-model For issues related to data model spec:metrics Related to the specification/metrics directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#1711 opened May 18, 2021 by jsuereth
17
Controlling context propagation boundary area:api Cross language API specification issue spec:context Related to the specification/context directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#1633 opened Apr 20, 2021 by pmm-sumo
12
Glossary definitions for types of propagation area:api Cross language API specification issue release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:context Related to the specification/context directory spec:miscellaneous For issues that don't match any other spec label
#1627 opened Apr 19, 2021 by tsloughter
Define implicit and explicit context area:api Cross language API specification issue spec:context Related to the specification/context directory
#1540 opened Mar 12, 2021 by arminru
Consider consuming non-supported attribute value types area:api Cross language API specification issue spec:trace Related to the specification/trace directory
#1509 opened Mar 6, 2021 by carlosalberto
API for response headers area:api Cross language API specification issue spec:trace Related to the specification/trace directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#1355 opened Jan 20, 2021 by yurishkuro
11
Inheritable Attributes area:api Cross language API specification issue spec:miscellaneous For issues that don't match any other spec label triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#1337 opened Jan 13, 2021 by HaloFour
5
Make the Resource accessible to Logging Library SDK area:api Cross language API specification issue area:sdk Related to the SDK help wanted Extra attention is needed release:after-ga Not required before GA release, and not going to work on before GA spec:logs Related to the specification/logs directory spec:resource Related to the specification/resource directory
#1330 opened Jan 11, 2021 by vovencij
8
the example in define Tracing.Api.TracerProvider exists Ambiguity. area:api Cross language API specification issue priority:p3 Lowest priority level question Question for discussion release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:trace Related to the specification/trace directory
#1303 opened Dec 25, 2020 by wph95
1
Clarify how to avoid leaking context propagation area:api Cross language API specification issue release:after-ga Not required before GA release, and not going to work on before GA spec:context Related to the specification/context directory
#1255 opened Nov 23, 2020 by pmm-sumo
4
Split the data model into its own document? area:api Cross language API specification issue area:miscellaneous For issues that don't match any other area label priority:p3 Lowest priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:trace Related to the specification/trace directory
#1253 opened Nov 20, 2020 by rakyll
1
Clarify behavior for null value in baggage. area:api Cross language API specification issue priority:p2 Medium priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:baggage Related to the specification/baggage directory
#1243 opened Nov 19, 2020 by bogdandrutu
ProTip! Add no:assignee to see everything that’s not assigned.