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

544 Open 1,124 Closed
544 Open 1,124 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

Update spec to permit negative observations of native/exponential histograms? spec:metrics Related to the specification/metrics directory
#4155 opened Jul 22, 2024 by callumj
[Logs] Reporting log bridge name and version area:semantic-conventions Related to semantic conventions spec:logs Related to the specification/logs directory
#4154 opened Jul 22, 2024 by pellared
@pellared
3
Document how consumers should identify browser telemetry spec:miscellaneous For issues that don't match any other spec label triage:deciding:community-feedback
#4145 opened Jul 12, 2024 by martinkuba
2
Refine only logs reads are permitted section spec:logs Related to the specification/logs directory triage:deciding:tc-inbox
#4141 opened Jul 11, 2024 by pellared
@pellared
Environment variables to provide K8s container and pod name spec:miscellaneous For issues that don't match any other spec label triage:deciding:tc-inbox
#4140 opened Jul 11, 2024 by iskiselev
2
Clarify how export retry should be implemented spec:trace Related to the specification/trace directory triage:deciding:tc-inbox
#4138 opened Jul 10, 2024 by brettmc
2
Clarification on SimpleProcessor concurrency spec:logs Related to the specification/logs directory spec:trace Related to the specification/trace directory triage:deciding:tc-inbox
#4134 opened Jul 9, 2024 by pellared
@cijothomas
4
Clarify how Application Developers are supposed to set the Span status when using Instrumentation Libraries spec:trace Related to the specification/trace directory triage:deciding:tc-inbox
#4131 opened Jul 7, 2024 by fkoep
7
[Terminology] Provide a term for a language-specific solution that adds otel to an application without the need of changing the code of the application itself. triage:deciding:tc-inbox
#4129 opened Jul 4, 2024 by svrnm
2
Baggage API: unclear sentence triage:deciding:tc-inbox
#4127 opened Jul 3, 2024 by tigrannajaryan
2
Add support for bound instruments to the metrics API spec:metrics Related to the specification/metrics directory triage:deciding:tc-inbox
#4126 opened Jul 2, 2024 by jack-berg
8
Should zero-duration spans be considered good/reasonable practice? spec:trace Related to the specification/trace directory triage:deciding:community-feedback
#4123 opened Jul 1, 2024 by lmolkova
7
[Terminology] Add a term to the glossary that describes when "Instrumented Library_and Instrumentation Library are the same" spec:miscellaneous For issues that don't match any other spec label triage:deciding:tc-inbox
#4089 opened Jun 27, 2024 by svrnm
8
[Triage Process] Allow SIG maintainers to express their requirements spec:miscellaneous For issues that don't match any other spec label triage:deciding:tc-inbox
#4083 opened Jun 20, 2024 by svrnm
3
How can we find critically blocking distributed tracing spans? (Should we add previous_sibling_span_id as an optional span attribute?) triage:deciding:community-feedback
#4079 opened Jun 12, 2024 by magicmark
12
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
#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 spec:miscellaneous For issues that don't match any other spec label
#4073 opened Jun 11, 2024 by svrnm
4
[entities-wg] Rubric for evaluation of Entity signal designs spec:miscellaneous For issues that don't match any other spec label triage:accepted:ready-with-sponsor
#4071 opened Jun 6, 2024 by jsuereth
@jsuereth
4
Log record mutations are visible in next registered processors spec:logs Related to the specification/logs directory triage:accepted:ready-with-sponsor
#4065 opened May 31, 2024 by pellared
1
@pellared
17
[Prometheus Compatibility] Reconsider 1 to ratio unit conversion sig-issue 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
#4058 opened May 23, 2024 by dashpole
@jsuereth
Adding a means to denote preference for Link vs Span in given Context spec:trace Related to the specification/trace directory triage:deciding:community-feedback
#4054 opened May 19, 2024 by hibachrach
8
DataPoint Flags are not mentioned in the Metrics Data Model area:data-model For issues related to data model spec:metrics Related to the specification/metrics directory triage:accepted:ready
#4053 opened May 17, 2024 by mx-psi
1
@pyohannes
4
Sampler API V2: What, Why, and How? area:sampling Related to trace sampling sig-issue spec:trace Related to the specification/trace directory triage:deciding:community-feedback
#4044 opened May 10, 2024 by kalyanaj
@jmacd
1
Clarify Attributes instrument advisory parameter spec:metrics Related to the specification/metrics directory triage:accepted:ready
#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
#4029 opened May 1, 2024 by chalin
1
4
ProTip! Find all open issues with in progress development work with linked:pr.