Proto commits in open-telemetry/opentelemetry-proto

These commits are when the Protocol Buffers files have changed: (only the last 100 relevant commits are shown)

2026-06-26

profiles: Add better doc and samples for the period_type / period fields. (#791)

The documentation is generated from this commit.

2026-06-24

profiles: improve documentation on single value without timestamp (#811) Signed-off-by: Florian Lehner <florian.lehner@elastic.co>

2026-06-16

processcontext: add `ProcessContext` message from OTEP 4719 (#783) Co-authored-by: Florian Lehner <florianl@users.noreply.github.com> Co-authored-by: Robert Pająk <pellared@hotmail.com>

2026-06-01

Minor documentation updates to profiles.proto (#780)

2026-05-22

profiles: improve Link message encoding documentation (#792)

2026-05-19

docs: Fix link to UCUM website (#758)

2026-03-18

Declare profiling alpha (#775) Co-authored-by: Roger Coll <roger.coll@elastic.co>

2026-03-03

[common] rename _ref suffix to _strindex (#768) Rename the experimental profiling field suffix from _ref _to _strindex to align with the naming in the profiles proto. Signed-off-by: Florian Lehner <florian.lehner@elastic.co>

2026-02-25

[resource] introduce reference based attributes (#733) * [resource] introduce reference based attributes Reduce duplicate entries by using a reference based approach in combination with a lookup table. Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * add missing dict_attributes field name * Apply suggestion from @florianl * Apply suggestion from @florianl * use reference in AnyValue Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * fix import path Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * fixup: add new line Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * rename fields Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * restructure reference based approach Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * drop strindex in AnyValue Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * apply https://docs.google.com/document/d/1v-XlgxnyyIsT-azCsfHJdRzVx-Ei2bIKB4hrYZQ6rGE Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * drop reference in AnyValue.oneof approach Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * return to AnyRefValue approach Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * fix field number Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * revert to AnyValue approach Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * drop remaining comment Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * extend comment Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * add reference to KeyValue Signed-off-by: Florian Lehner <florian.lehner@elastic.co> --------- Signed-off-by: Florian Lehner <florian.lehner@elastic.co> Co-authored-by: Felix Geisendörfer <felix.geisendoerfer@datadoghq.com>

2025-12-01

Clarify the profile and sample timestamps relationship. (#744)

profiles: clarify Sample message usage guidance docs. (#742) --------- Co-authored-by: Alexey Alexandrov <aalexand@users.noreply.github.com>

2025-11-20

logs: SEVERITY_NUMBER_UNSPECIFIED can be used as severity_number is optional (#736) * logs: SEVERITY_NUMBER_UNSPECIFIED can be used as severity_number is optional * add PR number * Fix typo in CHANGELOG.md --------- Co-authored-by: Josh Suereth <Joshua.Suereth@gmail.com>

profiles: improve Sample message clarity and usage documentation. (#724) * profiles: improve Sample message clarity and usage documentation. * profiles: improve Sample message clarity and usage documentation. Co-authored-by: Christos Kalkanis <christos.kalkanis@elastic.co> * profiles: improve Sample message clarity and usage documentation. Co-authored-by: Christos Kalkanis <christos.kalkanis@elastic.co> * profiles: improve Sample message clarity and usage documentation. * profiles: improve Sample message clarity and usage documentation. --------- Co-authored-by: Christos Kalkanis <christos.kalkanis@elastic.co> Co-authored-by: Alexey Alexandrov <aalexand@users.noreply.github.com> Co-authored-by: Josh Suereth <Joshua.Suereth@gmail.com>

2025-10-31

Clarify dictionary guidelines: duplicates and orphaned items (#732) Co-authored-by: Liudmila Molkova <neskazu@gmail.com>

2025-10-29

profiles: drop profile.comment_strindices (#729) Follow up as https://github.com/open-telemetry/semantic-conventions/pull/2861 go merged. Signed-off-by: Florian Lehner <florian.lehner@elastic.co> Co-authored-by: Liudmila Molkova <neskazu@gmail.com>

2025-10-28

Fix schema_url comments to include scope field coverage (#727) The schema_url field applies to both the instrumentation scope and the telemetry data fields, not just the telemetry data. Updated comments in all four signal proto files (logs, trace, metrics, profiles) to accurately reflect this. Co-authored-by: Liudmila Molkova <neskazu@gmail.com>

2025-10-27

all: drop attribute values restrictions (#707) * all: drop attribute values restrictions * add changelog entry * revert wording * revert wording * Revise changelog with important attribute values note * more explicit changelog entry * Update CHANGELOG.md * Update CHANGELOG.md * Update CHANGELOG.md

2025-10-22

[profiles] Clarify the original payload field comments. (#722) * Clarify the original payload field comments.

2025-09-22

Fixes #207 - Add Style guide for proto comments. (#717) * Fixes #207 - Add Style guide for proto comments. * Update comments to match style guide. * Fixes from review. * Update opentelemetry/proto/metrics/v1/metrics.proto Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com> --------- Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2025-09-16

Add a note about cardinality implications for attribute values. (#713)

2025-09-13

Document more explicitly the dictionary zero element requirement. (#711) Right now we have a comment to the dictionary proto and a comment to the string_table field. This requirement is important enough I think that it's worth documenting it more explicitly, especially the part that even if there are no references to the particular dictionary, the zero index element must still be present.

2025-09-05

Rename line -> lines and sample -> samples since these are repeated fields (#712)

Remove aggregation temporality enum and field. (#710)

2025-08-27

Profiles: simplify profile stack trace representation (ASCII fix, conflicts resolved) (#708) * Simplify profile stack trace representation - Introduce a first-class Stack message type and lookup table. - Replace location index range based stack trace encoding on Sample with a single stack_index reference. - Remove the location_indices lookup table. The primary motivation is laying the ground work for [timestamp based profiling][timestamp proposal] where the same stack trace needs to be referenced much more frequently compared to aggregation based on low cardinality attributes. Timestamp based profiling is also expected to be used with the the upcoming [Off-CPU profiling][off-cpu pr] feature in the eBPF profiler. Off-CPU stack traces have a different distribution compared to CPU samples. In particular stack traces are much more repetitive because they only occur at call sites such as syscalls. For the same reason it is also uncommon to see a stack trace are a root-prefix of a previously observed stack trace. We might need to revisit the previous [previous benchmarks][benchmarks] to confirm these claims. The secondary motivation is simplicitly. Arguably the proposed change here will make it easier to write exporters, processors as well as receivers. It seems like we had rough consensus around this change in previous SIG meetings, and it seems like a good incremental step to make progress on the timestamp proposal. [timestamp proposal]: https://github.com/open-telemetry/opentelemetry-proto/pull/594 [off-cpu pr]: https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/196 [benchmarks]: https://docs.google.com/spreadsheets/d/1Q-6MlegV8xLYdz5WD5iPxQU2tsfodX1-CDV1WeGzyQ0/edit?gid=2069300294#gid=2069300294 Modified-by: Christos Kalkanis <christos.kalkanis@elastic.co> * Update ASCII diagram for new Stack message * Move leaf frame explanation to field inside Stack message * Update field number * Update ASCII diagram (Sample->Stack n-1 instead of 1-1) --------- Co-authored-by: Felix Geisendörfer <felix@felixge.de>

2025-08-21

profiles: improve attribute encoding in ProfilesDictionary (#672) Subsequent to #659 (profiles: avoid 'optional' keyword usage) and in accordance with discussions in the profiling SIG, this PR updates the dictionary message docs to impose a more consistent handling of 'null pointer' semantics in the encoding pattern.

2025-08-14

Move zero-element comment about dictionary tables (#698)

Unsigned Profile time_nanos and duration_nanos (#692) We are already using unsigned type for [Sample.timestamps_unix_nano](https://github.com/open-telemetry/opentelemetry-proto/blob/b14635e74b7909c9f55db39666c667d4ea3092b7/opentelemetry/proto/profiles/v1development/profiles.proto#L422-L424) but not for the time-related fields in [Profile](https://github.com/open-telemetry/opentelemetry-proto/blob/b14635e74b7909c9f55db39666c667d4ea3092b7/opentelemetry/proto/profiles/v1development/profiles.proto#L235-L237). Also see: - #691

2025-08-12

profiles: Clarify ProfilesDictionary table[0] element use docs. (#688) Makes clear that all dictionary table fields should encode a 'null' element at index 0, such that optional fields pointing into the tables can use 0 value to indicate null.

all: add notes about the attribute values restrictions (#683)

2025-08-11

profiles: drop Location.is_folded (#690) Similar to the boolean attributes `Mapping.has_*` (https://github.com/open-telemetry/opentelemetry-proto/pull/595 and https://github.com/open-telemetry/semantic-conventions/pull/2522) also drop `Location.is_folded`. The complementary PR for the OTel SemConv, that builds on top of https://github.com/open-telemetry/semantic-conventions/pull/2522 is https://github.com/florianl/semantic-conventions/pull/1 Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2025-08-08

updated ScopeProfiles to Profiles relationship to 1-n (#684) Updated the relationship between `ScopeProfiles` and `Profile` from 1-1 to 1-n in the relationships diagram. This is a documentation-only change that fixes the diagram to accurately reflect the actual data model. The protobuf message definition shows: ``` message ScopeProfiles { // The instrumentation scope information for the profiles in this message. // Semantically when InstrumentationScope isn't set, it is equivalent with // an empty instrumentation scope name (unknown). opentelemetry.proto.common.v1.InstrumentationScope scope = 1; // A list of Profiles that originate from an instrumentation scope. repeated Profile profiles = 2; ... } ``` The `repeated Profile profiles` field indicates a one-to-many relationship, where a single `ScopeProfiles` can contain multiple `Profile` instances. The inconsistency in the diagram seems to have originated [here](https://github.com/open-telemetry/opentelemetry-proto/commit/7312bdf63218acf27fe96430b7231de37fd091f2) when removing `ProfileContainer`.

2025-08-07

Replace has_* fields with an enum. (#595) The has_* debug info fields were derived from the pprof format. We decided to move them to attributes, see https://github.com/open-telemetry/semantic-conventions/pull/2522.

2025-08-06

profiles: remove default_sample_type (#679) This resolves the ambiguity when a `ScopesProfiles` message contains more than one `profiles` entry matching the `default_sample_type`. Also add a comment to clarify which profile viewers should display by default. This was previously also ambiguous. This change creates a minor problem when it comes to ensuring that pprof profiles can round-trip through otel conversion as it may require the `ScopeProfiles.profiles` entries to be reordered in order to honor the `default_sample_type` of the original pprof message. Naively converting the resulting otel profile back to pprof would cause the order of `Profile.sample_types` to be changed. Merging this change indiciates consensus within the profiling group that this issue should be handled by adding a `pprof.profile_order` attribute (name TBD) to the `ScopeProfiles.attributes` during the initial pprof->otel conversion. This label will allow converting the resulting otel profile back to pprof without any information loss. See [gh-633][] for additional details. [gh-633]: https://github.com/open-telemetry/opentelemetry-proto/issues/633#issuecomment-3056622636 Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2025-07-02

profiles: use single Profile.sample_type and clarify use of timestamps (#649) Implements https://github.com/open-telemetry/opentelemetry-proto/issues/633#issuecomment-2772648117.

2025-06-27

profiles: make profile_id optional (#665) Fixes #652 Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2025-06-12

profiles: avoid 'optional' keyword usage (#659) Prefer reference tables with an explicit null/unused entry at index=0, rather than 'optional' pointers into the tables. Following discussion in the profiling SIG, we note that other OpenTelemetry signal types don't use 'optional' protobuf fields and, whilst the Dictionary lookup tables pattern in the profile signal type require some form of 'null pointer' value for indicating unset indexes into the tables, the string_table convention inherited from pprof prefers table[0] = "" i.e. treats a 0 value pointer as null. In the interest of improving consistency with other signal types and within the profiling signal itself, we therefore make mapping and link tables/references follow the same convention of having an explicit 'not used' default value as the first element in the dictionary table. Note that I've chosen to not update the docs for the other dictionary tables to require the same use of the [0] slot, as at present no _index fields optionally reference into them, so I'm treating it as unnecessary at this time. However, it can be argued that greater clarity and consistency would be achieved by making the convention universal in anticipation before adoption becomes widespread and it gets harder to change.

2025-05-26

profiles: drop gzip requirement (#661) There is no need for us to specifiy compression requirements on OpenTelemetry profiles. This should be defined by OTLP, see [spec]. For #629 [spec]: https://opentelemetry.io/docs/specs/otlp/#protocol-details Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2025-05-15

Move the profiles lookup tables into a new Dictionary message (#650)

2025-04-24

profiles: Move lookup tables to ProfilesData (#644) Implements https://github.com/open-telemetry/opentelemetry-proto/issues/628#issuecomment-2772566325. Signed-off-by: Florian Lehner <florian.lehner@elastic.co> Co-authored-by: Felix Geisendörfer <felix.geisendoerfer@datadoghq.com> Co-authored-by: Nayef Ghattas <11560964+Gandem@users.noreply.github.com>

2025-04-10

Stabilize event_name in LogRecord (#643)

2025-03-28

remove comment on each profile service about keeping the RPC alive (#637) Tigran explained this comment was likely a hold over from the OpenCensus protobufs which did use streaming RPC's. Unary RPC's, which are used by the OpenTelemetry protocol, can not be kept alive making the comment out of place. Co-authored-by: Josh Suereth <Joshua.Suereth@gmail.com>

Add EntityRef and use it in Resource. (#635) * Add EntityRef and use it in Resource. * Update opentelemetry/proto/resource/v1/resource.proto Co-authored-by: Nathan L Smith <nathan.smith@elastic.co> * Update opentelemetry/proto/common/v1/common.proto Co-authored-by: Nathan L Smith <nathan.smith@elastic.co> * Update opentelemetry/proto/common/v1/common.proto Co-authored-by: Nathan L Smith <nathan.smith@elastic.co> --------- Co-authored-by: Nathan L Smith <nathan.smith@elastic.co>

2025-03-26

profiles: clarify use of optional fields in message Line and message Function (#621)

2025-02-24

Update metrics.proto (#632)

2025-02-12

Clarify when bucket_counts array may be empty (#619) The current definition says: "The number of elements in bucket_counts array must be by one greater than the number of elements in explicit_bounds array." However, it also says "bucket_counts is an optional field", which means its length can be 0, which than in turn means the length of explicit_bounds must be -1, which is impossible. We clarify that it is a valid situation to have both bucket_counts and explicit_bounds arrays empty.

2025-02-11

profiles: switch default sample type index from string_table to sample_type array (#620) Signed-off-by: Florian Lehner <florian.lehner@elastic.co> Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2025-02-04

[editorial] Use canonical URL to OpenMetrics repo (#617)

2025-01-09

Simplify profile stack trace representation - Introduce a first-class Stack message type and lookup table. - Replace location index range based stack trace encoding on Sample with a single stack_index reference. - Remove the location_indices lookup table. The primary motivation is laying the ground work for [timestamp based profiling][timestamp proposal] where the same stack trace needs to be referenced much more frequently compared to aggregation based on low cardinality attributes. Timestamp based profiling is also expected to be used with the the upcoming [Off-CPU profiling][off-cpu pr] feature in the eBPF profiler. Off-CPU stack traces have a different distribution compared to CPU samples. In particular stack traces are much more repetitive because they only occur at call sites such as syscalls. For the same reason it is also uncommon to see a stack trace are a root-prefix of a previously observed stack trace. We might need to revisit the previous [previous benchmarks][benchmarks] to confirm these claims. The secondary motivation is simplicitly. Arguably the proposed change here will make it easier to write exporters, processors as well as receivers. It seems like we had rough consensus around this change in previous SIG meetings, and it seems like a good incremental step to make progress on the timestamp proposal. [timestamp proposal]: https://github.com/open-telemetry/opentelemetry-proto/pull/594 [off-cpu pr]: https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/196 [benchmarks]: https://docs.google.com/spreadsheets/d/1Q-6MlegV8xLYdz5WD5iPxQU2tsfodX1-CDV1WeGzyQ0/edit?gid=2069300294#gid=2069300294

2024-12-13

update links to openmetrics to reference the v1.0.0 release (#612)

profile: drop duplicate field in message Profile (#606) * profile: drop duplicate field in message Profile The message Profile contains two fields of type `opentelemetry.proto.common.v1.KeyValue`, `attribute_table` and `attributes`. Both fields are intended for the same use. Therefore drop the later one. * fixup: add attribute_indices to message Profile Signed-off-by: Florian Lehner <florian.lehner@elastic.co> * fixup: move comment Signed-off-by: Florian Lehner <florian.lehner@elastic.co> --------- Signed-off-by: Florian Lehner <florian.lehner@elastic.co> Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>

2024-12-11

Add `event_name` to logs proto (#600) * Add event_name to log proto

2024-12-10

Add note about schema url and schema version (#605)

2024-11-22

Remove unused label from profiles (#602)

2024-11-08

Renovations to experimental profiling schema. (#596) - remove Profile keep_frames and drop_frames due to unclear semantics and use cases - make Sample.link_index and Location.mapping_index optional, consistent with documented intention - remove deprecated fields Sample.location_index, Mapping.id, Location.id, Function.id - renumber fields for improved redability

2024-11-04

Improve lookup table pattern use in profiles. (#592) Based on implementation experience with the draft version of the profiles spec, the use of lookup tables for storing values is space efficient but not particularly user friendly. This change makes improvements by changing field names to clarify their role in the pattern and changing their data types to better accommodate their use in languages limited to 32 bit array indexing e.g. Java.

2024-10-15

Fold the content of pprofextended.proto into profiles.proto, removing ProfileContainer. (#590) This change removes the now unnecessary split of the profiling format between two files, combining them into one as with other protocols. In the process, the likewise unnecessary ProfileContainer message type is removed and its fields merged into Profile, saving one level of indirection. Note this as discussed on slack otel-profiles, this is effectively a minimal subset of the now defunct #587, remaining parts of which will be resubmitted in subsequent PRs. This PR effectively blocks any concurrent changes to pprofextended.proto e.g. #588 as git won't track such changes across the file 'merge'.

2024-10-01

Clarify aggregation temporality for Summary metric type (#591)

2024-09-26

profiles: Make mapping in Profile optional (#556) As commented in [0] and discussed in the OTel Profiling SIG meeting, there are situations where a main binary for a Profile can not be identified. For these cases mark the field optional. FYI: @brancz @petethepig @open-telemetry/profiling-maintainers [0]: https://github.com/open-telemetry/opentelemetry-proto/pull/534#discussion_r1561141336

2024-09-24

Rename profiles v1experimental to v1development (#585) As discussed in https://github.com/open-telemetry/opentelemetry-proto/pull/582#discussion_r1751850589, this renames the `v1experimental` version for profiles to `v1development`. I've also taken this opportunity to update the versioning and stability link.

2024-09-16

profiles: drop BuildIdKind (#584) Drop `BuildIdKind` in favor of its semantic convention as defined in https://github.com/open-telemetry/semantic-conventions/pull/1329. Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

profiles: drop Sample.label (#583) Drop `Sample.label` in favor of `Sample.attributes`. While `label` and `attributes` fulfill the same purpose, it is not defined which one choose for which information. Therefore, drop `label` in favor of `attributes`. FYI: @open-telemetry/profiling-maintainers spec:profiles Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

profiles: drop Location.type_index (#578) With https://github.com/open-telemetry/semantic-conventions/pull/1188 the semantic convention for Profiles that introduces frame types and well known values is about to be merged. Therefore, `Location.type_index` is no longer needed. FYI: @open-telemetry/profiling-maintainers Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2024-09-04

profiles: drop Sample.stacktrace_id_index (#575) The value for Sample.stacktrace_id_index is hardly defined except for its length. It is also not defined how this value should be generated, interpreted and could be used. Some kind of stacktrace_id can be most efficient in stateful protocols, where transmitting duplicate information should be avoided. As the OTel Profiling protocol is a stateless protocol, this element can be droped.

2024-08-13

profiles: align type of index into string table (#557) With `Mapping.filename`, `Function.name`, `Label.key` and others the type of the index into the string table is always of type `int64`. For consistency align the type of `Location.type_index`, which is also an index into the string table, to `int64`. Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

2024-07-02

Add resource attributes and scope to metrics proto diagram (#519) Fixes https://github.com/open-telemetry/opentelemetry-proto/issues/518.

2024-06-05

Fix typo; According to the definition of message Sample, the relation between Sample and Link should be n-1 (#564)

2024-05-13

profiles: add missing java_package option to pprofextended. (#558) Gah, we put java_package on one file but not the other. Oops. Apparently the opentelementry-proto-java artifact can't be consumed by opentelemetry-java without this.

2024-04-23

Add new profile signal (#534) This is a follow up to [OTEP 239: Introduces Profiling Data Model v2](https://github.com/open-telemetry/oteps/pull/239) The main motivation behind this PR is that this will allow us to start experimenting with the profiles proto in opentelemetry-collector. I marked the profiles part as `Experimental` to indicate that this is not a final version of the data model. I copied the proto from the OTEP, and moved `pprofextended.proto` from `profiles/v1/alternatives/pprofextended.proto` to just `profiles/v1/pprofextended.proto`. I did this because I figured we no longer have alternative representations and this will reduce confusion for people outside of Profiling SIG. The rest of the proto stayed the same. I tested this file with a collector fork and I it compiles properly.

2024-02-02

Add metric.metadata for supporting additional metadata on metrics (#514) * add metric.attributes for supporting additional metadata on metrics

2024-01-30

Clarify formulas for reading span flags (#528) * Add bitshift to comment for reading span flags * Change >> to != 0

2024-01-23

Merge parent and link is remote enums into one

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Christian Neumüller <christian+github@neumueller.me>

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>

Use enum for ParentSpanIsRemote

Adjust enum name

Add constants and enum for interpreting bits 8 and 9 of a Link's flags

Remove misleading documentation

Update names

Remove ParentSpanIsRemote attribute

Change doc references to updated enum name

Adjust flags documentation ordering

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>

Update references to isremote masks

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>

Adjust formatting of comments

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Johannes Tax <johannes@johannes.tax>

Update opentelemetry/proto/trace/v1/trace.proto Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>

Include enum for interpreting ParentIsRemote flag and update documentation

Split isremote into two masks

Remove enum, describe values in comment

Add extra comment about unset value from older clients

Add parent_span_is_remote to Span message

Update inconsistency in docs formatting

Add defintion of 2 bit parent is remote flag

One constant for link and parent is remote mask

2023-11-07

Remove irrelevant comments from metric name field (#512)