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

567 Open 1,158 Closed
567 Open 1,158 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

Support measurement processors in Metrics SDK spec:metrics Related to the specification/metrics directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4298 opened Nov 18, 2024 by Blinkuu
5
Page feedback - exporter (delimiters) triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
#4296 opened Nov 17, 2024 by sparecycles
3
[non-normative] Answer commonly asked judgement questions for defining Specification 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
#4293 opened Nov 13, 2024 by jsuereth
@jsuereth
Migrate OTEPs to the Specification repository 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
#4284 opened Nov 7, 2024 by carlosalberto
3 of 6 tasks
Clarify that exporter timeout settings must be positive 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 triage:followup Needs follow up during triage
#4283 opened Nov 5, 2024 by jack-berg
1
[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
Event identifier of an integer type sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4278 opened Nov 4, 2024 by pellared
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
Remove the sentence of discouraging direct use of Logger.Emit method area:api Cross language API specification issue sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4275 opened Oct 30, 2024 by XSAM
3
It should be possible to propagate context without creating a new span spec:trace Related to the specification/trace directory triage:accepted:ready-with-sponsor Ready to be implemented and has a specification sponsor assigned
#4271 opened Oct 22, 2024 by lmolkova
@lmolkova
2
Resource/Entity merge logic prevents fine-grained detectors entities sig-issue A specific SIG should look into this before discussing at the spec
#4266 opened Oct 18, 2024 by tigrannajaryan
1
Prometheus exporter config -> type_suffix needs clarification sig-issue A specific SIG should look into this before discussing at the spec spec:metrics Related to the specification/metrics directory
#4265 opened Oct 17, 2024 by psx95
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
3
Add Event Enabled operation to Logger area:api Cross language API specification issue sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4263 opened Oct 15, 2024 by pellared
SeverityNumber as required parameter in EmitEvent area:api Cross language API specification issue sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4261 opened Oct 15, 2024 by pellared
Add EventName to Log and Event Record in data model area:data-model For issues related to data model sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4260 opened Oct 15, 2024 by pellared
5
Add Context parameter to Enabled for metrics instruments area:api Cross language API specification issue spec:metrics Related to the specification/metrics directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4256 opened Oct 11, 2024 by pellared
1
22
Truly auto 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
#4255 opened Oct 11, 2024 by ostrolucky
9
[entities] Do we always require identifying attributes to be globally unique? entities sig-issue A specific SIG should look into this before discussing at the spec
#4254 opened Oct 10, 2024 by dmitryax
1
[entities] Do we allow different identifying attributes? entities sig-issue A specific SIG should look into this before discussing at the spec
#4253 opened Oct 10, 2024 by dmitryax
Metric aggregation env variables are only for OTLP Exporter 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 triage:followup Needs follow up during triage
#4248 opened Oct 8, 2024 by cijothomas
5
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
Document interoperability for OpenTelemetry sampling specifications sig-issue A specific SIG should look into this before discussing at the spec spec:trace Related to the specification/trace directory
#4243 opened Oct 3, 2024 by jmacd
1
Define TraceState handling for root spans with NewRootTraceState option sig-issue A specific SIG should look into this before discussing at the spec spec:trace Related to the specification/trace directory
#4241 opened Oct 3, 2024 by jmacd
1
Define whether instrumentations can emit non-event log records area:api Cross language API specification issue sig-issue A specific SIG should look into this before discussing at the spec spec:logs Related to the specification/logs directory
#4234 opened Sep 30, 2024 by pellared
5
ProTip! Add no:assignee to see everything that’s not assigned.