Skip to content

Issues: open-telemetry/opentelemetry-proto

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

27 Open 167 Closed
27 Open 167 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 requirements to meet before EntityRef is added to the Resource
#603 opened Nov 21, 2024 by tigrannajaryan
4 tasks
2
Specify whether resource envelopes containing no telemetry points are valid OTLP
#598 opened Nov 13, 2024 by isaaczinda
9
ExportLogsServiceRequest JSON example may be invalid
#579 opened Aug 30, 2024 by demurgos
3
Follow up: breaking changes in the Profiling protocol spec:profiles
#577 opened Aug 23, 2024 by florianl
2
Clarify flags meaning
#574 opened Aug 20, 2024 by bogdandrutu
Probably unintentional proto field ID gaps in the Sample message in pprofextended spec:profiles
#562 opened May 18, 2024 by aalexand
@petethepig
profiling spec - definition of common string values spec:profiles
#555 opened May 3, 2024 by jhalliday
3
Why is AggregationTemporality redefined pprofextended.proto spec:profiles
#547 opened Apr 24, 2024 by jack-berg
2
Consider generalizing profile attributes optimization to other signals spec:profiles
#546 opened Apr 18, 2024 by jack-berg
Fix outdated attribute examples in comments
#543 opened Apr 4, 2024 by jack-berg
Specify version of the proto that introduced a field in the comments
#535 opened Mar 21, 2024 by tigrannajaryan
Supporting JSON as-is encoding in OTLP
#524 opened Jan 9, 2024 by scheler
2
Generated OpenAPI files wrongly encode enums
#517 opened Dec 15, 2023 by bripkens
Allow consumers to use map<string, AnyValue> instead of repeated KeyValue
#515 opened Nov 30, 2023 by punya
3
Unclear whether Span.flags represents span's parent or own flags spec:traces
#507 opened Sep 19, 2023 by Oberon00
@jmacd
10
Clarify whether OTLP/gRPC codes should cover both client and server
#506 opened Sep 6, 2023 by carlosalberto
1
Add ability for OTLP to indicate which records were rejected for retryable reasons
#470 opened May 8, 2023 by joshdover
@yurishkuro
5
Clarify in otlp.md that timestamps in JSON are also fixed64 help wanted Extra attention is needed
#460 opened Apr 28, 2023 by tigrannajaryan
1
Add version identification to the opentelemetry-proto tar archive
#434 opened Oct 28, 2022 by marcalff
1
Just for maintainers information
#431 opened Oct 17, 2022 by bogdandrutu
6
encoding of context flags in otlp messages
#382 opened Apr 19, 2022 by blumamir
1
14
Clarify what is the correlation between Sum/Gauge NumberDataPoint value and Exemplar value area:data-model spec:metrics
#319 opened Jul 19, 2021 by bogdandrutu
1
Allow sum to present with negative measurements in Histogram area:data-model enhancement New feature or request release:after-ga Not required before GA release, and not going to work on before GA spec:metrics
#303 opened May 8, 2021 by jsuereth
1
3
Metrics Number data points requirements for value area:data-model release:allowed-for-ga Editorial changes that can still be added to the GA spec since they don't require action by SIGs spec:metrics
#286 opened Mar 26, 2021 by bogdandrutu
@jmacd
2
Consistent style for documentation comments release:after-ga Not required before GA release, and not going to work on before GA
#207 opened Aug 21, 2020 by anuraaga
2
ProTip! Add no:assignee to see everything that’s not assigned.