Skip to content

Issues: open-telemetry/opentelemetry-specification

Beta
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

576 Open 1,227 Closed
576 Open 1,227 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
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Stabilize EventName parameter of Logger.Enabled sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4528 opened May 27, 2025 by pellared
@pellared
1
Accurate and Efficient Approach for Calculating OTel Log Record Size spec:logs Related to the specification/logs directory
#4522 opened May 22, 2025 by liustve
Prometheus Metric points to OTLP to include native histograms with exponential buckets spec:metrics Related to the specification/metrics directory
#4520 opened May 21, 2025 by krajorama
Question about gRPC error handling specification spec:protocol Related to the specification/protocol directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#4513 opened May 16, 2025 by DylanRussell
9
Dependency Dashboard triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4507 opened May 13, 2025 by renovate bot
4 tasks
Stabilize Tracer.Enabled 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
#4501 opened May 9, 2025 by pellared
Avoiding conflicting context headers spec:context Related to the specification/context directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#4496 opened May 6, 2025 by dyladan
Update Prometheus spec based on new updates in upstream Prometheus sig-issue A specific SIG should look into this before discussing at the spec spec:metrics Related to the specification/metrics directory
#4494 opened May 5, 2025 by ywwg
5 tasks
@dashpole
3
Stabilize scope configuration ({Signal}Config, {Signal}Configurator) 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
#4491 opened May 2, 2025 by brunobat
2
Document AnyValue attribute limits spec:logs Related to the specification/logs directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#4487 opened Apr 24, 2025 by lmolkova
[entities] contradiction between resource and entity attributes sig-issue A specific SIG should look into this before discussing at the spec spec:resource Related to the specification/resource directory
#4486 opened Apr 23, 2025 by dyladan
@dyladan
4
Define SpanProcessor emitting span lifecycle events area:sdk Related to the SDK enhancement New feature or request spec:trace Related to the specification/trace directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4483 opened Apr 17, 2025 by pellared
[protocol/exporter] allow SDK users to enrich the user-agent header in exporters spec:protocol Related to the specification/protocol directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4479 opened Apr 11, 2025 by david-luna
3
Additional severity range applicable to logs with missing severity level spec:logs Related to the specification/logs directory triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4478 opened Apr 10, 2025 by Vincehood
2
@pellared
4
Zipkin transformation to support resource and instrumentation scope attributes spec:trace Related to the specification/trace directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4473 opened Apr 7, 2025 by ysolomchenko
4
Add an EnvVarPropagator decorator with example code for the env context specification spec:context Related to the specification/context directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4470 opened Apr 2, 2025 by adrielp
2 tasks done
1
2
Review the language around standard attributes (and breaking changes) maintainer-request Escalated by SIG maintainers triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4468 opened Mar 28, 2025 by lmolkova
@lmolkova
10
Stabilize reuse of Standard Attributes in Logs API maintainer-request Escalated by SIG maintainers spec:logs Related to the specification/logs directory triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4460 opened Mar 26, 2025 by pellared
1
@pellared
4
Document the default behavior on whether Trace SDK (and sugar around it) should record exceptions 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
#4455 opened Mar 22, 2025 by lmolkova
2
Update resource model in versioning and stability specification. area:data-model For issues related to data model area:semantic-conventions Related to semantic conventions spec:miscellaneous For issues that don't match any other spec label 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
#4451 opened Mar 17, 2025 by jsuereth
@jsuereth
Endorse use of runtime-defined instrumentation scope 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
#4450 opened Mar 13, 2025 by jade-guiton-dd
1
@carlosalberto
4
Metrics Data Model: Diagrams are difficult to read in dark mode triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4449 opened Mar 13, 2025 by smith
5
Clarify that map values are unordered area:data-model For issues related to data model 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
#4443 opened Mar 7, 2025 by anuraaga
4
How to handle additional exporter config parameters area:configuration Related to configuring the SDK sig-issue A specific SIG should look into this before discussing at the spec
#4440 opened Mar 4, 2025 by mattsains
6
The Batching Processor is missing details which are in the Trace Batching Processor 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
#4434 opened Feb 26, 2025 by JDUNNIN
ProTip! Add no:assignee to see everything that’s not assigned.