Bump OTLP proto files to 1.10.0 (#7018)

Author: Kielek

src/Shared/Proto/opentelemetry/proto/common/v1/common.proto

@@ -36,6 +36,17 @@ message AnyValue {
     ArrayValue array_value = 5;
     KeyValueList kvlist_value = 6;
     bytes bytes_value = 7;
+    // Reference to the string value in ProfilesDictionary.string_table.
+    //
+    // Note: This is currently used exclusively in the Profiling signal.
+    // Implementers of OTLP receivers for signals other than Profiling should
+    // treat the presence of this value as a non-fatal issue.
+    // Log an error or warning indicating an unexpected field intended for the
+    // Profiling signal and process the data as if this value were absent or
+    // empty, ignoring its semantic content for the non-Profiling signal.
+    //
+    // Status: [Development]
+    int32 string_value_strindex = 8;
   }
 }
 
@@ -65,10 +76,24 @@ message KeyValueList {
 // attributes, etc.
 message KeyValue {
   // The key name of the pair.
+  // key_ref MUST NOT be set if key is used.
   string key = 1;
 
   // The value of the pair.
   AnyValue value = 2;
+
+  // Reference to the string key in ProfilesDictionary.string_table.
+  // key MUST NOT be set if key_strindex is used.
+  //
+  // Note: This is currently used exclusively in the Profiling signal.
+  // Implementers of OTLP receivers for signals other than Profiling should
+  // treat the presence of this key as a non-fatal issue.
+  // Log an error or warning indicating an unexpected field intended for the
+  // Profiling signal and process the data as if this value were absent or
+  // empty, ignoring its semantic content for the non-Profiling signal.
+  //
+  // Status: [Development]
+  int32 key_strindex = 3;
 }
 
 // InstrumentationScope is a message representing the instrumentation scope information

src/Shared/Proto/opentelemetry/proto/logs/v1/logs.proto

@@ -85,7 +85,6 @@ message ScopeLogs {
 
 // Possible values for LogRecord.SeverityNumber.
 enum SeverityNumber {
-  // UNSPECIFIED is the default SeverityNumber, it MUST NOT be used.
   SEVERITY_NUMBER_UNSPECIFIED = 0;
   SEVERITY_NUMBER_TRACE  = 1;
   SEVERITY_NUMBER_TRACE2 = 2;

src/Shared/Proto/opentelemetry/proto/profiles/v1development/profiles.proto

@@ -284,9 +284,14 @@ message Profile {
   // The following fields 3-12 are informational, do not affect
   // interpretation of results.
 
-  // Time of collection (UTC) represented as nanoseconds past the epoch.
+  // Time of collection. Value is UNIX Epoch time in nanoseconds since 00:00:00
+  // UTC on 1 January 1970.
   fixed64 time_unix_nano = 3;
-  // Duration of the profile, if a duration makes sense.
+  // Duration of the profile. For instant profiles like live heap snapshot, the
+  // duration can be zero but it may be preferable to set time_unix_nano to the
+  // process start time and duration_nano to the relative time when the profile
+  // was gathered. This ensures Sample.timestamps_unix_nano values such as
+  // allocation timestamp fall into the profile time range.
   uint64 duration_nano = 4;
   // The kind of events between sampled occurrences.
   // e.g [ "cpu","cycles" ] or [ "heap","bytes" ]
@@ -364,7 +369,11 @@ message ValueType {
 // both fields are populated, they MUST contain the same number of elements, and
 // the elements at the same index MUST refer to the same event.
 //
-// Examples of different ways of representing a sample with the total value of 10:
+// For the purposes of efficiently representing aggregated data observations, a Sample is regarded
+// as having a shared identity and an associated collection of per-observation data points.
+// Samples having the same identity SHOULD be combined by inserting timestamps and values to the data arrays.
+//
+// Examples of different ways ('shapes') of representing a sample with the total value of 10:
 //
 // Report of a stacktrace at 10 timestamps (consumers must assume the value is 1 for each point):
 //    values: []
@@ -377,20 +386,30 @@ message ValueType {
 // Report of a stacktrace at 4 timestamps where each point records a specific value:
 //    values: [2, 2, 3, 3]
 //    timestamps_unix_nano: [1, 2, 3, 4]
+//
+// All Samples for a Profile SHOULD have the same shape, i.e. all data observation series should consistently
+// adopt the same data recording style.
+//
 message Sample {
+
+  // A Sample's identity (i.e. 'primary key') is the tuple of {stack_index, set_of(attribute_indices), link_index}
+
   // Reference to stack in ProfilesDictionary.stack_table.
   int32 stack_index = 1;
-  // The type and unit of each value is defined by Profile.sample_type.
-  repeated int64 values = 2;
   // References to attributes in ProfilesDictionary.attribute_table. [optional]
-  repeated int32 attribute_indices = 3;
-
+  repeated int32 attribute_indices = 2;
   // Reference to link in ProfilesDictionary.link_table. [optional]
   // It can be unset / set to 0 if no link exists, as link_table[0] is always a 'null' default value.
-  int32 link_index = 4;
+  int32 link_index = 3;
 
-  // Timestamps associated with Sample represented in nanoseconds. These
-  // timestamps should fall within the Profile's time range.
+  // The following fields may contain per-observation data and do not form part of the Sample's identity.
+
+  // The type and unit of each value is defined by Profile.sample_type.
+  repeated int64 values = 4;
+  // Timestamps associated with Sample. Value is UNIX Epoch time in nanoseconds
+  // since 00:00:00 UTC on 1 January 1970. The timestamps should fall within the
+  // [Profile.time_unix_nano, Profile.time_unix_nano + Profile.duration_nano)
+  // time range.
   repeated fixed64 timestamps_unix_nano = 5;
 }