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.

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

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

Issues list

Allow UpDown counters to be 'set' release:after-ga Not required before GA release, and not going to work on before GA spec:metrics Related to the specification/metrics directory
#2054 opened Oct 24, 2021 by RichardWright
Support unit customization in Metrics View area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:metrics Related to the specification/metrics directory
#1822 opened Jul 20, 2021 by reyang
Return type of callback functions for Asynchronous Instruments area:api Cross language API specification issue release:after-ga Not required before GA release, and not going to work on before GA spec:metrics Related to the specification/metrics directory
#1732 opened May 28, 2021 by jonatan-ivanov
Review approach & specify algorithm for TraceIdRatioBasedSampler (ProbabilitySampler) area:sampling Related to trace sampling area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA sig-issue spec:trace Related to the specification/trace directory
#1413 opened Feb 9, 2021 by Oberon00
OTLP exporter concurrent sending requirements area:data-model For issues related to data model area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:metrics Related to the specification/metrics directory spec:protocol Related to the specification/protocol directory spec:trace Related to the specification/trace directory
#1405 opened Feb 5, 2021 by aabmass
Missing environment variables area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:miscellaneous For issues that don't match any other spec label
#1389 opened Jan 29, 2021 by ocelotl
Allow registering exporters without exposing BatchSpanProcessor as a type area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1331 opened Jan 11, 2021 by anuraaga
Make the Resource accessible to Logging Library SDK area:api Cross language API specification issue area:sdk Related to the SDK help wanted Extra attention is needed release:after-ga Not required before GA release, and not going to work on before GA spec:logs Related to the specification/logs directory spec:resource Related to the specification/resource directory
#1330 opened Jan 11, 2021 by vovencij
Add Sampler.shutdown area:sampling Related to trace sampling area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1295 opened Dec 17, 2020 by anuraaga
Include export timestamp to aid with inaccurate clocks area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:miscellaneous For issues that don't match any other spec label spec:protocol Related to the specification/protocol directory
#1270 opened Dec 1, 2020 by pmm-sumo
Consider making faas.id a span attribute instead of a resource attribute area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:resource Related to the specification/resource directory
#1261 opened Nov 26, 2020 by mateuszrzeszutek
Clarify how to avoid leaking context propagation area:api Cross language API specification issue release:after-ga Not required before GA release, and not going to work on before GA spec:context Related to the specification/context directory
#1255 opened Nov 23, 2020 by pmm-sumo
Suggest max size for the log body? area:sdk Related to the SDK help wanted Extra attention is needed release:after-ga Not required before GA release, and not going to work on before GA spec:logs Related to the specification/logs directory
#1251 opened Nov 20, 2020 by rakyll
Trace: FaaS PubSub specification - open question area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1228 opened Nov 16, 2020 by nirsky
Support for Jaeger's "firehose" flag. area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1226 opened Nov 13, 2020 by toumorokoshi
Support restarting the trace with a different trace ID area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1188 opened Nov 3, 2020 by yurishkuro
Provide a way for knowing when a Context is made current area:api Cross language API specification issue release:after-ga Not required before GA release, and not going to work on before GA spec:context Related to the specification/context directory spec:logs Related to the specification/logs directory
#1163 opened Oct 30, 2020 by HaloFour
Add StatusSource from OTEP 136 area:api Cross language API specification issue area:error-reporting Related to error reporting release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1092 opened Oct 14, 2020 by arminru
ExporterFactory, runtime exporter selection via connection string area:sdk Related to the SDK release:after-ga Not required before GA release, and not going to work on before GA spec:miscellaneous For issues that don't match any other spec label spec:trace Related to the specification/trace directory
#1071 opened Oct 7, 2020 by dkarlovi
Clarify why would analysis tools generate errors? area:api Cross language API specification issue release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1068 opened Oct 6, 2020 by bogdandrutu
Notify SpanProcessor when Event added to Span area:sdk Related to the SDK enhancement New feature or request release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1041 opened Sep 30, 2020 by HaloFour
Indicate which semantic conventions generate errors. area:error-reporting Related to error reporting area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
#1003 opened Sep 25, 2020 by carlosalberto
Getters and Setters being "optional helpers" passed to a TextMapPropagator is unclear area:api Cross language API specification issue question Question for discussion release:after-ga Not required before GA release, and not going to work on before GA spec:context Related to the specification/context directory
#986 opened Sep 22, 2020 by arminru
Functions for modifying a Composite Propagator release:after-ga Not required before GA release, and not going to work on before GA spec:context Related to the specification/context directory
#954 opened Sep 15, 2020 by alanwest
Specify behavior of async resource detection release:after-ga Not required before GA release, and not going to work on before GA spec:resource Related to the specification/resource directory
#952 opened Sep 15, 2020 by dyladan
ProTip! Add no:assignee to see everything that’s not assigned.