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
21 Open 37 Closed
21 Open 37 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

Conditions to rename attributes, metrics, and events in stable semconv area:miscellaneous For issues that don't match any other area label area:semantic-conventions Related to semantic conventions needs discussion Need more information before all suitable labels can be applied question Question for discussion triage:deciding:community-feedback
#3513 opened May 17, 2023 by lmolkova
1
Schema transformation process should be able to preserve original attributes area:miscellaneous For issues that don't match any other area label spec:miscellaneous For issues that don't match any other spec label triage:deciding:community-feedback
#3510 opened May 17, 2023 by lmolkova
3
Define best practices for no-code configuration area:miscellaneous For issues that don't match any other area label
#1773 opened Jun 23, 2021 by carlosalberto
@MrAlias
17
Clarify strings across the spec area:miscellaneous For issues that don't match any other area label spec:miscellaneous For issues that don't match any other spec label
#1587 opened Mar 29, 2021 by reyang
2
The spec should not impose object-oriented paradigms area:miscellaneous For issues that don't match any other area label bug Something isn't working spec:trace Related to the specification/trace directory
#1569 opened Mar 22, 2021 by reyang
CONTRIBUTING.md should mention Go 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:miscellaneous For issues that don't match any other spec label
#1394 opened Feb 1, 2021 by iNikem
Provide a policy for language and component release cadences area:miscellaneous For issues that don't match any other area label 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:miscellaneous For issues that don't match any other spec label
#1338 opened Jan 11, 2021 by jkwatson
@carlosalberto
6
Consistent formatting of terms 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:miscellaneous For issues that don't match any other spec label
#1271 opened Dec 2, 2020 by chulkilee
4
Use consistent format for concepts in Trace API doc area:miscellaneous For issues that don't match any other area label bug Something isn't working 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
#1263 opened Nov 30, 2020 by chulkilee
1
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
Set encoding rules for bytes represented in text and JSON 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:protocol Related to the specification/protocol directory
#1252 opened Nov 20, 2020 by rakyll
4
Make it possible to automatically list all specification requirements area:miscellaneous For issues that don't match any other area label 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:miscellaneous For issues that don't match any other spec label
#1210 opened Nov 9, 2020 by ocelotl
75 tasks
2
OpenTelemetry Implementation Compatibility 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:miscellaneous For issues that don't match any other spec label
#1153 opened Oct 28, 2020 by HaloFour
2
Contrib directory for vendor specific specifications area:miscellaneous For issues that don't match any other area label 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:miscellaneous For issues that don't match any other spec label
#1110 opened Oct 19, 2020 by tsloughter
1
@tsloughter
5
Consider distinguishing between API and SDK in the spec compliance matrix area:miscellaneous For issues that don't match any other area label help wanted Extra attention is needed 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:miscellaneous For issues that don't match any other spec label
#1088 opened Oct 13, 2020 by arminru
@bogdandrutu
2
Revert #1043 (Third Party Propagators location) area:miscellaneous For issues that don't match any other area label 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:context Related to the specification/context directory
#1047 opened Oct 1, 2020 by carlosalberto
@carlosalberto @alolita
13
How should OpenTelemetry-internal metrics be exposed? area:miscellaneous For issues that don't match any other area label 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:metrics Related to the specification/metrics directory
#959 opened Sep 16, 2020 by toumorokoshi
7
Add overview entry for auto instrumentation(s) area:miscellaneous For issues that don't match any other area label release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#805 opened Aug 14, 2020 by Oberon00
Guidelines for changelog entries? area:miscellaneous For issues that don't match any other area label release:after-ga Not required before GA release, and not going to work on before GA
#656 opened Jun 15, 2020 by Oberon00
3
Changelog entries create merge conflicts area:miscellaneous For issues that don't match any other area label question Question for discussion release:after-ga Not required before GA release, and not going to work on before GA
#655 opened Jun 15, 2020 by Oberon00
1
Define conventions for Registry types. area:miscellaneous For issues that don't match any other area label enhancement New feature or request needs discussion Need more information before all suitable labels can be applied 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
#595 opened May 11, 2020 by austinlparker
1
ProTip! no:milestone will show everything without a milestone.