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
26 Open 9 Closed
26 Open 9 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

[editorial] Hugo front matter is missing from new configuration/sdk.md page editorial Editorial changes only (typos, changelog, ...). No content-related changes of any kind. triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4232 opened Sep 27, 2024 by chalin
[Prometheus and OpenMetrics] Handle scheme URL and scope attributes as identifying sig-issue A specific SIG should look into this before discussing at the spec spec:metrics Related to the specification/metrics directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4223 opened Sep 24, 2024 by pellared
@dashpole @pellared
3
Not clear to which messages a schema url applies to spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4180 opened Aug 6, 2024 by lukasmalkmus
2
Transition from .md to .yml for Issue Templates triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4165 opened Jul 29, 2024 by Venkatesh-Krishnan-R
3
[Triage Process] Allow SIG maintainers to express their requirements spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4083 opened Jun 20, 2024 by svrnm
1
7
Versioning and stability > Signal lifecycle: image still uses "experimental" status, and some statuses missing spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4076 opened Jun 11, 2024 by chalin
2 tasks
Clarify Attributes instrument advisory parameter spec:metrics Related to the specification/metrics directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4037 opened May 7, 2024 by pichlermarc
1
1
[Editorial] Inline Hugo front matter editorial Editorial changes only (typos, changelog, ...). No content-related changes of any kind. triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4029 opened May 1, 2024 by chalin
1
4
No clear API defined for resource detector libraries spec:resource Related to the specification/resource directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4016 opened Apr 26, 2024 by joaopgrassi
6
Log section of spec compliance matrix is inconsistent spec:logs Related to the specification/logs directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4013 opened Apr 25, 2024 by jack-berg
Update CONTRIBUTING.md regarding removed auto-assign workflow editorial Editorial changes only (typos, changelog, ...). No content-related changes of any kind. triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3968 opened Mar 29, 2024 by arminru
Alignment with OpenTelemetry Collector configuration area:configuration Related to configuring the SDK triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3963 opened Mar 25, 2024 by mx-psi
3 of 4 tasks
@mx-psi
3
Metrics Multiple-Instruments callback requirements missing from spec-compliance-matrix spec:metrics Related to the specification/metrics directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3942 opened Mar 14, 2024 by marcalff
Clarification on SeverityText Usage Relative to Recommended Short Names clarification clarify ambiguity in specification spec:logs Related to the specification/logs directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3933 opened Mar 8, 2024 by 10xLaCroixDrinker
2
[file configuration] Escaping environment variable substitution area:configuration Related to configuring the SDK sig-issue A specific SIG should look into this before discussing at the spec spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3914 opened Feb 29, 2024 by pellared
7
Specification & OTEP relationship: Provide references to implemented OTEPs spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3792 opened Dec 14, 2023 by svrnm
24 of 46 tasks
7
Stabilize "attributes" instrument advisory parameter spec:metrics Related to the specification/metrics directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3785 opened Dec 7, 2023 by trask
7
Conflicting/confusing requirements around InstrumentationScope attributes spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3773 opened Nov 17, 2023 by breedx-splk
@jack-berg
6
Improve histogram images in metrics data-model.md help wanted Extra attention is needed spec:metrics Related to the specification/metrics directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3745 opened Oct 27, 2023 by breedx-splk
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
Consistency of the term used to express data point kind, instrument kind area:data-model For issues related to data model area:sdk Related to the SDK editorial Editorial changes only (typos, changelog, ...). No content-related changes of any kind. help wanted Extra attention is needed spec:metrics Related to the specification/metrics directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#3555 opened Jun 14, 2023 by sebastien-rosset
1
Clarify cardinality requirements of a span name 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
#3534 opened Jun 2, 2023 by lmolkova
9
Clarify acceptable values for span status ERROR descriptions 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
#3496 opened May 10, 2023 by trask
Request for adoption in OTel SDKs of the W3C Trace Context Level 2 spec (which is now in Candidate Recommendation status) 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
#3411 opened Apr 18, 2023 by kalyanaj
10
Clarify precedence of attributes when exporting to non-OTLP formats spec:miscellaneous For issues that don't match any other spec label triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#2535 opened May 12, 2022 by tigrannajaryan
1
3
ProTip! Mix and match filters to narrow down what you’re looking for.