-
Notifications
You must be signed in to change notification settings - Fork 994
All issues
Issue creation is restricted in this repository
- #5264 · opentelemetry-pr-dashboard opened
on Aug 11, 2026
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#5267 In open-telemetry/opentelemetry-specification;
The ComposableAlwaysRecord sampler is missing
spec:traceRelated to the specification/trace directoryRelated to the specification/trace directoryStatus: Open.#5266 In open-telemetry/opentelemetry-specification;Pull Request Dashboard
dashboardPull request dashboardPull request dashboardStatus: Open.#5264 In open-telemetry/opentelemetry-specification;Why Exporter.ForceFlush and Exporter.Shutdown MUST be safe to be called concurrently?
area:sdkRelated to the SDKRelated to the SDKspec:logsRelated to the specification/logs directoryRelated to the specification/logs directoryStatus: Open.#5248 In open-telemetry/opentelemetry-specification;Consider classifying context-scoped attributes so providers can filter them
spec:contextRelated to the specification/context directoryRelated to the specification/context directoryStatus: Open.#5247 In open-telemetry/opentelemetry-specification;File exporter: should an existing file be appended to or truncated?
spec:protocolRelated to the specification/protocol directoryRelated to the specification/protocol directoryStatus: Open.#5243 In open-telemetry/opentelemetry-specification;Add a skill for reviewing spec compliance
triage:deciding:community-feedbackOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedtriage:followupNeeds follow up during triageNeeds follow up during triageStatus: Open.#5226 In open-telemetry/opentelemetry-specification;Clarify Telemetry Policy update behaviour for sets of policies
spec:miscellaneousFor issues that don't match any other spec labelFor issues that don't match any other spec labeltriage:deciding:community-feedbackOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedtriage:followupNeeds follow up during triageNeeds follow up during triageStatus: Open.#5218 In open-telemetry/opentelemetry-specification;Clarify expected behavior for empty/whitespace-only span names
spec:traceRelated to the specification/trace directoryRelated to the specification/trace directorytriage:deciding:community-feedbackOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedStatus: Open.#5215 In open-telemetry/opentelemetry-specification;Fix issues related to
OTEL_ENTITIESand maturity levelsig-issueA specific SIG should look into this before discussing at the specA specific SIG should look into this before discussing at the specspec:resourceRelated to the specification/resource directoryRelated to the specification/resource directoryStatus: Open.#5209 In open-telemetry/opentelemetry-specification;Multiple issues could be closed
triage:accepted:readyReady to be implemented. Small enough or uncontroversial enough to be implemented without sponsorReady to be implemented. Small enough or uncontroversial enough to be implemented without sponsorStatus: Open.#5207 In open-telemetry/opentelemetry-specification;Consider bi-directional context-scoped attribute propagation
spec:contextRelated to the specification/context directoryRelated to the specification/context directorytriage:deciding:community-feedbackOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedOpen to community discussion. If the community can provide sufficient reasoning, it may be acceptedStatus: Open.#5187 In open-telemetry/opentelemetry-specification;