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

585 Open 1,194 Closed
585 Open 1,194 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

Clarify that map values are unordered area:data-model For issues related to data model 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
#4443 opened Mar 7, 2025 by anuraaga
1
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
1
Decide how semantic conventions for Entities should be defined entities triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4436 opened Feb 27, 2025 by jsuereth
@jsuereth
1
Logs specification seems inconsistent spec:logs Related to the specification/logs directory triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4435 opened Feb 27, 2025 by yasmin-aumeeruddy
1
@pellared
1
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
Record span-ending exceptions as span attributes instead of span event or log sig-issue A specific SIG should look into this before discussing at the spec
#4429 opened Feb 24, 2025 by alexmojaki
26
Bridging/embedding requirements for configuration area:configuration Related to configuring the SDK sig-issue A specific SIG should look into this before discussing at the spec
#4428 opened Feb 21, 2025 by zeitlinger
2
[project tracking] We need a new Telemetry Schema specification 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
#4427 opened Feb 19, 2025 by jsuereth
1 of 4 tasks
@jsuereth
10
Proposal: Adding messaging publish(send) and process wrapper API and matched instrumentation. 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
#4426 opened Feb 19, 2025 by Cirilla-zmh
Add SpanContext.IsSampled to spec 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
#4425 opened Feb 19, 2025 by loganrosen
2
Where are the Feature Flag semantic conventions for spans in the v1.30 spec? sig-issue A specific SIG should look into this before discussing at the spec spec:trace Related to the specification/trace directory
#4419 opened Feb 17, 2025 by julealgon
5
Recording details as logs, span events, or span attributes triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#4414 opened Feb 11, 2025 by lmolkova
28
Env variable vs code - precedence area:configuration Related to configuring the 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
#4413 opened Feb 11, 2025 by cijothomas
7
Spec how composite sampler works with legacy head-based sampling sig-issue A specific SIG should look into this before discussing at the spec spec:trace Related to the specification/trace directory
#4411 opened Feb 10, 2025 by yuanyuanzhao3
Requirements of distributions for configuration area:configuration Related to configuring the SDK sig-issue A specific SIG should look into this before discussing at the spec
#4416 opened Feb 10, 2025 by zeitlinger
9
Should the Metrics minimum goals be updated in the docs? triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4405 opened Feb 7, 2025 by shawnstephens
@reyang
1
Add more description for OTEL_BSP_SCHEDULE_DELAY triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4402 opened Feb 5, 2025 by JDUNNIN
1
5
Define how SDK implements Enabled for synchronous instruments spec:metrics Related to the specification/metrics directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#4398 opened Feb 4, 2025 by pellared
Define how SDK implements 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
#4397 opened Feb 4, 2025 by pellared
Support for OTLP/UDP Span Exporter 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
#4396 opened Feb 4, 2025 by jj22ee
3
Document span events <-> log-based events conversion sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4393 opened Feb 1, 2025 by lmolkova
8
Logs data model canonical OTLP encoding for null any values maintainer-request Escalated by SIG maintainers sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4392 opened Jan 30, 2025 by aabmass
2
Support disabled-by-default metrics using an advisory parameter. spec:metrics Related to the specification/metrics directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#4391 opened Jan 30, 2025 by dashpole
9
Limited OTLP exporter request authentication methods 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
#4390 opened Jan 29, 2025 by majanjua-amzn
8
Add ability to limit resource attribute length in metrics spec:metrics Related to the specification/metrics directory triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
#4378 opened Jan 20, 2025 by zeitlinger
ProTip! Updated in the last three days: updated:>2025-03-07.