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
100 Open 128 Closed
100 Open 128 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

Migrate OTEPs to the Specification repository spec:miscellaneous For issues that don't match any other spec label
#4284 opened Nov 7, 2024 by carlosalberto
6 tasks
[configuration] Force type when doing environment variable substitution spec:miscellaneous For issues that don't match any other spec label triage:deciding:needs-info Not enough information. Left open to provide the author with time to add more details
#4281 opened Nov 4, 2024 by flyfire2002
3
Do we need to specify what implementations must exist before marking capabilties Stable? spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4276 opened Oct 31, 2024 by tigrannajaryan
1
11
Add SDK env variable for OTLP TLS skip verify 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
#4264 opened Oct 17, 2024 by pavolloffay
2
TLS certificate reloading in SDK 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
#4247 opened Oct 8, 2024 by pavolloffay
3
Add specification for managing sessions 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
#4198 opened Sep 2, 2024 by martinkuba
12
Support :? shell syntax for 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-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4190 opened Aug 19, 2024 by yurishkuro
2
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
Environment variables to provide K8s container and pod name 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
#4140 opened Jul 11, 2024 by iskiselev
@jsuereth
7
[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
Add GitHub workflow, that helps SIG maintainers to keep track of spec changes help wanted Extra attention is needed 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
#4073 opened Jun 11, 2024 by svrnm
4
[Prometheus Compatibility] Reconsider 1 to ratio unit conversion sig-issue A specific SIG should look into this before discussing at the spec spec:metrics Related to the specification/metrics directory spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4058 opened May 23, 2024 by dashpole
@jsuereth
Stabilize Telemetry Stability document 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
#3998 opened Apr 17, 2024 by pellared
1
Schema transformation: type mismatch/conversion should be specified 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
#3992 opened Apr 10, 2024 by lmolkova
How to reflect experimental features to spec compliance matrix spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#3976 opened Apr 2, 2024 by jack-berg
@reyang
7
Clarify backward compatibility requirements when introducing new capabilities spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#3954 opened Mar 22, 2024 by tigrannajaryan
@tigrannajaryan
12
Clarify the valid content in primitive type string 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 triage:deciding:needs-info Not enough information. Left open to provide the author with time to add more details
#3950 opened Mar 20, 2024 by XSAM
1
16
Env var resource configuration should be RECOMMENDED and not optional area:configuration Related to configuring the SDK area:sdk Related to the SDK spec:miscellaneous For issues that don't match any other spec label spec:resource Related to the specification/resource directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3929 opened Mar 7, 2024 by lmolkova
3
[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
Rework spec issue management spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#3821 opened Jan 12, 2024 by jack-berg
@tedsuo @dyladan
7
AttributeValueLengthLimit needs more clarity for non-string types 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
#3818 opened Jan 11, 2024 by tigrannajaryan
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
Service renaming 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 spec:resource Related to the specification/resource directory
#3791 opened Dec 14, 2023 by LikeTheSalad
@carlosalberto
11
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
ProTip! Type g i on any issue or pull request to go back to the issue listing page.