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

Clear current search query, filters, and sorts
40 Open 1 Closed
40 Open 1 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

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
15
Update spec to permit negative observations of native/exponential histograms? spec:metrics Related to the specification/metrics directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4155 opened Jul 22, 2024 by callumj
6
Clarify how Application Developers are supposed to set the Span status when using Instrumentation Libraries spec:metrics Related to the specification/metrics directory spec:trace Related to the specification/trace directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4131 opened Jul 7, 2024 by fkoep
15
[Terminology] Provide a term for a language-specific solution that adds otel to an application without the need of changing the code of the application itself. triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4129 opened Jul 4, 2024 by svrnm
6
Baggage API: unclear sentence triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4127 opened Jul 3, 2024 by tigrannajaryan
3
Use ABNF syntax instead of PCRE2 in file configuration env var substitution syntax area:configuration Related to configuring the SDK sig-issue A specific SIG should look into this before discussing at the spec triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4027 opened Apr 30, 2024 by jack-berg
1
Stable instrumentations can change produced telemetry for bugfixes triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#4005 opened Apr 22, 2024 by pellared
1
Stabilize Telemetry Stability document spec:miscellaneous For issues that don't match any other spec label triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3998 opened Apr 17, 2024 by pellared
1
Schema transformation: type mismatch/conversion should be specified spec:miscellaneous For issues that don't match any other spec label triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3992 opened Apr 10, 2024 by lmolkova
Deprecate environment variables which do not interoperate with file config when ready for stabilization area:configuration Related to configuring the SDK triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3967 opened Mar 28, 2024 by jack-berg
@jack-berg
Control baggage propagation in automatic instrumentation libraries spec:baggage Related to the specification/baggage directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3957 opened Mar 22, 2024 by robotadam
6
Env var resource configuration should be RECOMMENDED and not optional area:configuration Related to configuring the SDK area:sdk Related to the SDK spec:miscellaneous For issues that don't match any other spec label spec:resource Related to the specification/resource directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3929 opened Mar 7, 2024 by lmolkova
3
Retryable HTTP Statuses should be configurable in OTLP clients spec:protocol Related to the specification/protocol directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3876 opened Feb 14, 2024 by haus
2
Are buckets optional in OTLP Exponential Histograms? spec:metrics Related to the specification/metrics directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3848 opened Jan 29, 2024 by mx-psi
3
Move SDK requirements from semconv to spec spec:resource Related to the specification/resource directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3839 opened Jan 23, 2024 by jpkrohling
2
AttributeValueLengthLimit needs more clarity for non-string types spec:miscellaneous For issues that don't match any other spec label triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3818 opened Jan 11, 2024 by tigrannajaryan
Default aggregation should mention "Attributes" from instrument advisory spec:metrics Related to the specification/metrics directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3790 opened Dec 13, 2023 by cijothomas
Clarify what to do on non-reversible telemetry schema downgrades spec:miscellaneous For issues that don't match any other spec label triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3727 opened Oct 19, 2023 by mx-psi
5
What should be the schema URL merge behavior when a resource is empty (no attributes) spec:resource Related to the specification/resource directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3710 opened Oct 2, 2023 by joaopgrassi
6
Identify Links added after Span creation spec:trace Related to the specification/trace directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3698 opened Sep 20, 2023 by carlosalberto
4
Allow Optional Retries Using Persistent Store for OTLP Exporter spec:protocol Related to the specification/protocol directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3645 opened Aug 7, 2023 by vishweshbankwar
3
Clarify and improve the OTLP exporter requirements of a retry strategy spec:protocol Related to the specification/protocol directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3639 opened Aug 3, 2023 by alanwest
5
Metrics SDK: allow metric readers to filter Meters during Collect() spec:metrics Related to the specification/metrics directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3617 opened Jul 24, 2023 by marcalff
@yurishkuro
6
Metrics SDK: allow several metric readers to share the same metric exporter spec:metrics Related to the specification/metrics directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3616 opened Jul 24, 2023 by marcalff
13
SpanEvent and Event through LogRecord should be "unified" spec:logs Related to the specification/logs directory spec:trace Related to the specification/trace directory triage:accepted:needs-sponsor Ready to be implemented, but does not yet have a specification sponsor
#3406 opened Apr 17, 2023 by jsuereth
21
ProTip! What’s not been updated in a month: updated:<2024-10-14.