chore : Document all the types and fields of model.proto by chethanm99 · Pull Request #187 · jaegertracing/jaeger-idl

chethanm99 · 2026-02-28T11:28:53Z

Description of the changes

TODO in this file says to document all the fields and types. So I have added comments describing each field and types.

Checklist

I have read https://github.com/jaegertracing/jaeger/blob/main/CONTRIBUTING_GUIDELINES.md
I have signed all commits
I have added unit tests for the new functionality
I have run lint and test steps successfully: make lint test

AI Usage in this PR (choose one)

See AI Usage Policy.

None: No AI tools were used in creating this PR
Light: AI provided minor assistance (formatting, simple suggestions)
Moderate: AI helped with code generation or debugging specific parts
Heavy: AI generated most or all of the code changes

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

This PR adds documentation comments to proto/api_v2/model.proto to describe the purpose of key message/enum types and several fields in Jaeger’s API v2 protobuf model.

Changes:

Added doc comments for core model enums/messages (e.g., ValueType, KeyValue, Span, Trace, Batch, DependencyLink).
Added per-field documentation for several identifiers and timestamps/durations (e.g., trace_id, span_id, start_time, duration).
Updated comments around batching/relationships to better explain span and service dependencies.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-28T11:30:56Z

proto/api_v2/model.proto

+//ValueType describes the type of value stored in a key-value pair.
 enum ValueType {


New doc comments are missing a space after // (e.g., //ValueType). The rest of this repo’s .proto comments use // with a space; please update the newly added comments for consistent formatting.

Copilot · 2026-02-28T11:30:56Z

proto/api_v2/model.proto

 }

+//Log is a time-stamped event which captures the incidents such as errors,
+//lifecycle events that occured during the execution of the span in key-value format.


Spelling: "occured" should be "occurred".

Suggested change

//lifecycle events that occured during the execution of the span in key-value format.

//lifecycle events that occurred during the execution of the span in key-value format.

Copilot · 2026-02-28T11:30:56Z

proto/api_v2/model.proto

  SpanRefType ref_type = 3;
 }

+//Process represents the service that resuted in the creation of span.


Spelling: "resuted" should be "resulted".

Suggested change

//Process represents the service that resuted in the creation of span.

//Process represents the service that resulted in the creation of span.

Copilot · 2026-02-28T11:30:56Z

proto/api_v2/model.proto

    (gogoproto.customtype) = "TraceID",
    (gogoproto.customname) = "TraceID"
  ];
+  //span_id indentifies the ID of the span.


Spelling: "indentifies" should be "identifies".

Suggested change

//span_id indentifies the ID of the span.

//span_id identifies the ID of the span.

Copilot · 2026-02-28T11:30:56Z

proto/api_v2/model.proto

    repeated Span spans = 1;
    Process process = 2 [
      (gogoproto.nullable) = true
    ];


The indentation inside message Batch looks off (the spans and process fields are indented more than other messages in this file). Please align indentation to match the surrounding proto style to avoid noisy diffs/formatting issues.

Suggested change

repeated Span spans = 1;

Process process = 2 [

(gogoproto.nullable) = true

];

repeated Span spans = 1;

Process process = 2 [

(gogoproto.nullable) = true

];

Copilot · 2026-02-28T11:30:57Z

proto/api_v2/model.proto

  BINARY  = 4;
 };

+//KeyValue is a message type used to store dynamically-typed attributes under a single structure.


The file-level // TODO: document all types and fields comment is still present near the top of this file. Since this PR’s stated goal is to complete that documentation, consider removing or updating the TODO to avoid implying the work is still incomplete.

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 11 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-03T07:46:30Z

proto/api_v2/model.proto

+//Process represents the service that resulted in the creation of span.
 message Process {
+  //service_name represents the name of the service which resulted in creation of span.
  string service_name = 1;
+  //tags describe the metadata about the service such as Host, IP, Environment etc.


The Process message comments are missing spaces after // and have some grammar/capitalization issues (e.g., “creation of span” → “creation of a span”, “Host, IP, Environment etc.”). Please adjust wording and punctuation so the docs read cleanly.

Suggested change

//Process represents the service that resulted in the creation of span.

message Process {

//service_name represents the name of the service which resulted in creation of span.

string service_name = 1;

//tags describe the metadata about the service such as Host, IP, Environment etc.

// Process represents the service that resulted in the creation of a span.

message Process {

// service_name represents the name of the service that resulted in the creation of a span.

string service_name = 1;

// tags describe metadata about the service, such as host, IP address, environment, etc.

Copilot · 2026-03-03T07:46:31Z

proto/api_v2/model.proto

    (gogoproto.customtype) = "SpanID",
    (gogoproto.customname) = "SpanID"
  ];
+  //It represents the name of the operation.


operation_name comment (“It represents…”) is vague and doesn’t mention the field name, and it’s missing a space after //. Suggest phrasing like // operation_name is ... (matching style in sampling.proto) and avoid ambiguous pronouns.

Suggested change

//It represents the name of the operation.

// operation_name is the name of the operation.

Copilot · 2026-03-03T07:46:31Z

proto/api_v2/model.proto

@@ -142,6 +164,7 @@
        (gogoproto.nullable) = false
      ];
  }
+  //spans represent the spans within the trace.
  repeated Span spans = 1;


Trace/field comments here are missing spaces after // (e.g., //Trace, //spans) and have minor grammar issues (“collection of spans with same trace ID”). Please adjust to consistent doc-comment style and wording.

Copilot · 2026-03-03T07:46:31Z

proto/api_v2/model.proto

+//Batch represents the group of spans sent to Jaeger over a wire.
 message Batch {
-    repeated Span spans = 1;
-    Process process = 2 [
-      (gogoproto.nullable) = true
-    ];
+  //It represents the spans within the batch.
+  repeated Span spans = 1;
+  Process process = 2 [
+    (gogoproto.nullable) = true
+  ];


Batch message/field comments are missing spaces after //, and //It represents the spans... is vague. Also, if the intent is to document all fields, process (field 2) still has no comment.

Copilot · 2026-03-03T07:46:31Z

proto/api_v2/model.proto

+//Log is a time-stamped event which captures the incidents such as errors,
+//lifecycle events that occurred during the execution of the span in key-value format.
 message Log {


The Log message comment is missing spaces after // and reads a bit ungrammatically (e.g., “captures the incidents such as errors”). Consider rephrasing to a complete sentence and keep comment formatting consistent with the other proto files (space after //, wrapped lines).

Copilot · 2026-03-03T07:46:32Z

proto/api_v2/model.proto

@@ -142,6 +164,7 @@
        (gogoproto.nullable) = false
      ];
  }


The nested ProcessMapping fields are indented inconsistently compared to the rest of the file (extra leading spaces on string process_id / Process process). Since this hunk is already being edited, please normalize indentation to match surrounding messages (2-space indent).

Copilot · 2026-03-03T07:46:32Z

proto/api_v2/model.proto

+//DependencyLink represents the relationship between the two services.
 message DependencyLink {
+  //parent represents the calling service.
  string parent = 1;
+  //child represents the called service.
  string child = 2;
+  //call_count represents the number of calls between the two services.
  uint64 call_count = 3;


DependencyLink comments are missing spaces after // (e.g., //DependencyLink, //parent, etc.). Please update to // DependencyLink ... / // parent ... for consistency with the rest of proto/api_v2.

Copilot · 2026-03-03T07:46:32Z

proto/api_v2/model.proto

  string    key      = 1;
  ValueType v_type    = 2;
  string    v_str     = 3;
  bool      v_bool    = 4;
  int64     v_int64   = 5;
  double    v_float64 = 6;
  bytes     v_binary  = 7;


This change removes the file-level TODO to document all types/fields, but many fields below still have no comments (e.g., KeyValue.key, v_type, v_str, etc.). Either complete field-level documentation throughout this file or keep the TODO so it’s clear the documentation work is still incomplete.

Copilot · 2026-03-03T07:46:32Z

proto/api_v2/model.proto

+//SpanRef describes the reference from one span to another, it
+//establishes relationship between the spans.


SpanRef comment has two issues: it’s missing a space after // and it’s a run-on sentence (“..., it establishes ...”). Please split into separate sentences and keep the comment format consistent.

Suggested change

//SpanRef describes the reference from one span to another, it

//establishes relationship between the spans.

// SpanRef describes the reference from one span to another.

// It establishes the relationship between the spans.

Copilot · 2026-03-03T07:46:33Z

proto/api_v2/model.proto

+  //trace_id represents the trace containing the referenced span.
  bytes trace_id = 1 [
    (gogoproto.nullable) = false,
    (gogoproto.customtype) = "TraceID",
    (gogoproto.customname) = "TraceID"
  ];
+  //span_id represents the referenced span within the trace.
  bytes span_id = 2 [
    (gogoproto.nullable) = false,
    (gogoproto.customtype) = "SpanID",
    (gogoproto.customname) = "SpanID"
  ];
+  //ref_type describes the type of relationship between the spans.
  SpanRefType ref_type = 3;


Field comments here are missing a space after // (e.g., //trace_id) and don’t follow the style used elsewhere in proto/api_v2 (// trace_id ...). Please update these (and similar new field comments throughout the file) for consistent formatting.

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 5 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-04T09:03:41Z

proto/api_v2/model.proto

+    string process_id = 1 [
        (gogoproto.customname) = "ProcessID"
-      ];
-      Process process = 2 [
+    ];
+     Process process = 2 [
        (gogoproto.nullable) = false
-      ];
+    ];


In Trace.ProcessMapping, indentation is inconsistent with the rest of this file (e.g., SpanRef.trace_id options are indented 2 spaces, with option lines aligned under the [), and there’s an extra leading space before Process process. This makes the proto harder to read/maintain—please normalize indentation to match surrounding messages.

Copilot · 2026-03-04T09:03:41Z

proto/api_v2/model.proto

  string parent = 1;
+  // child represents the called service.
  string child = 2;
+  //call_count represents the number of calls between the two services.


Missing space after // in the call_count field comment (//call_count ...). This looks like a typo/style issue and breaks consistency with the other comments in the file.

Suggested change

//call_count represents the number of calls between the two services.

// call_count represents the number of calls between the two services.

Copilot · 2026-03-04T09:03:41Z

proto/api_v2/model.proto

    (gogoproto.stdtime) = true,
    (gogoproto.nullable) = false
  ];
+  // duration represents how long did the span run.


Grammar in the new duration field comment is off (“how long did the span run”). Consider rephrasing to something like “duration represents how long the span ran” or “duration is the elapsed time of the span” for clarity.

Suggested change

// duration represents how long did the span run.

// duration represents how long the span ran.

Copilot · 2026-03-04T09:03:42Z

proto/api_v2/model.proto

@@ -112,36 +134,44 @@ message Span {
    (gogoproto.nullable) = false,
    (gogoproto.customtype) = "Flags"
  ];
+  // start_time represents the time when the span started.
  google.protobuf.Timestamp start_time = 6 [
    (gogoproto.stdtime) = true,
    (gogoproto.nullable) = false
  ];
+  // duration represents how long did the span run.
  google.protobuf.Duration duration = 7 [
    (gogoproto.stdduration) = true,
    (gogoproto.nullable) = false
  ];
+  // tags represents the metadata of the operation.
  repeated KeyValue tags = 8 [
    (gogoproto.nullable) = false
  ];
+  // logs represents the timestamped events within the span.
  repeated Log logs = 9 [
    (gogoproto.nullable) = false
  ];
+  // process represents the process which emitted the span.
  Process process = 10;
  string process_id = 11 [
    (gogoproto.customname) = "ProcessID"
  ];
  repeated string warnings = 12;
 }


The PR description/title says all types and fields are documented, but several fields in this file still have no comments (e.g., Log.fields, Span.references, Span.flags, Span.process_id, Span.warnings, Trace.process_map, Trace.warnings, and the fields inside ProcessMapping). Either add comments for the remaining fields or adjust the PR scope/description so it’s accurate.

Copilot · 2026-03-04T09:03:42Z

proto/api_v2/model.proto

  repeated string warnings = 12;
 }

+// Trace represents the collection of spans with same trace ID.


Minor grammar in the new Trace doc comment: “collection of spans with same trace ID” is missing an article. Consider “collection of spans with the same trace ID” for readability.

Suggested change

// Trace represents the collection of spans with same trace ID.

// Trace represents the collection of spans with the same trace ID.

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-04T09:28:56Z

proto/api_v2/model.proto

-      Process process = 2 [
+    ];
+    // process represents process definition along with service name and tags.
+     Process process = 2 [


The ProcessMapping block has inconsistent indentation, and there is an extra leading space before Process process = 2 that hurts readability. Please align indentation with the surrounding proto style.

Suggested change

Process process = 2 [

Process process = 2 [

Copilot · 2026-03-04T09:28:57Z

proto/api_v2/model.proto

  }
+  // The list of spans that belong to this trace.
  repeated Span spans = 1;
+  // process_map represents the mapping of process identifiers to thier process definitons.


Typo(s) in the field comment: "thier" and "definitons" should be corrected (e.g., "their process definitions").

Suggested change

// process_map represents the mapping of process identifiers to thier process definitons.

// process_map represents the mapping of process identifiers to their process definitions.

Copilot · 2026-03-04T09:28:57Z

proto/api_v2/model.proto

+  // ProcessMapping represents the name and tags of the service.
  message ProcessMapping {
-      string process_id = 1 [
+    // process_id is a unique identifier to each process in the trace.


This comment is grammatically incorrect: "a unique identifier to each process" should be reworded (e.g., "a unique identifier for each process").

Suggested change

// process_id is a unique identifier to each process in the trace.

// process_id is a unique identifier for each process in the trace.

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-04T09:34:47Z

proto/api_v2/model.proto


+// Trace represents the collection of spans with the same trace ID.
 message Trace {
+  // ProcessMapping represents the name and tags of the service.


The comment for ProcessMapping appears inaccurate: the nested message is a mapping from process_id to a Process, not directly "the name and tags of the service". Consider updating the comment to describe it as an ID-to-Process mapping.

Suggested change

// ProcessMapping represents the name and tags of the service.

// ProcessMapping represents a single mapping entry from a process_id

// to its Process definition (including service name and tags).

Copilot · 2026-03-04T09:34:47Z

proto/api_v2/model.proto

  ];
 }

+// Span represents the single operation performed within the trace.


"Span represents the single operation..." is slightly ungrammatical; consider "Span represents a single operation..." for clearer documentation.

Suggested change

// Span represents the single operation performed within the trace.

// Span represents a single operation performed within the trace.

Copilot · 2026-03-04T09:34:47Z

proto/api_v2/model.proto

+// Log is a time-stamped event which captures the incidents such as errors,
+// lifecycle events that occurred during the execution of the span in key-value format.


The Log message comment is grammatically unclear ("captures the incidents such as"). Consider rephrasing to something like "captures incidents such as errors or lifecycle events" to improve readability.

Suggested change

// Log is a time-stamped event which captures the incidents such as errors,

// lifecycle events that occurred during the execution of the span in key-value format.

// Log is a time-stamped event which captures incidents such as errors or lifecycle

// events that occur during the execution of the span in key-value format.

Copilot · 2026-03-04T09:34:48Z

proto/api_v2/model.proto


+// Span represents the single operation performed within the trace.
 message Span {
+  // trace_id identifies ID of the trace, all the spans within it share the same trace_id.


The comment for trace_id is awkwardly phrased ("identifies ID of the trace"). Consider rewording to "identifies the trace" / "is the trace ID" to make the sentence grammatical.

Suggested change

// trace_id identifies ID of the trace, all the spans within it share the same trace_id.

// trace_id is the ID of the trace; all the spans within it share the same trace_id.

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-04T09:40:40Z

proto/api_v2/model.proto

  bytes     v_binary  = 7;
 }

+// Log is a time-stamped event which captures incidents such as errors or lifecycles


In the Log message comment, "lifecycles events" is grammatically incorrect; it should be "lifecycle events".

Suggested change

// Log is a time-stamped event which captures incidents such as errors or lifecycles

// Log is a time-stamped event which captures incidents such as errors or lifecycle

Copilot · 2026-03-04T09:40:40Z

proto/api_v2/model.proto

  string process_id = 11 [
    (gogoproto.customname) = "ProcessID"
  ];
+  // Warnings generation during span creation.


The comment on the Span.warnings field reads "Warnings generation"; this should be "Warnings generated" (or similar) to match the intended meaning.

Suggested change

// Warnings generation during span creation.

// Warnings generated during span creation.

Copilot · 2026-03-04T09:40:40Z

proto/api_v2/model.proto

+    string process_id = 1 [
        (gogoproto.customname) = "ProcessID"
-      ];
-      Process process = 2 [
+    ];
+    // process represents process definition along with service name and tags.
+    Process process = 2 [
        (gogoproto.nullable) = false
-      ];
+    ];


Indentation inside the ProcessMapping field option blocks is inconsistent with the rest of this file (compare to Span.trace_id options). Align the option lines and closing bracket indentation to the same level used elsewhere to keep formatting consistent and avoid noisy diffs from auto-formatters.

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

proto/api_v2/model.proto:75

Log now has a message-level doc comment, but its fields (timestamp and fields) are still undocumented. Since the stated goal is to document all types and fields, please add field-level comments for these two fields (see style in proto/api_v2/sampling.proto where each field is documented).

// Log is a time-stamped event which captures incidents such as errors or lifecycle
// events that occur during the execution of the span in key-value format.
message Log {
  google.protobuf.Timestamp timestamp = 1 [
    (gogoproto.stdtime) = true,
    (gogoproto.nullable) = false
  ];
  repeated KeyValue fields = 2 [
    (gogoproto.nullable) = false

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-04T09:57:01Z

proto/api_v2/model.proto

+// Process represents the service that resulted in the creation of a span.
 message Process {
+  // service_name represents the name of the service that resulted in the creation of a span.
  string service_name = 1;
+  // tags describe the metadata about the service, such as host, IP address, environment etc.


The new Process doc comment says it "represents the service" but the message includes both service_name and tags and is referenced elsewhere as the process that emitted the span. Consider updating the message and service_name comments to describe the emitting process/service (service name + process-level tags) to avoid under-documenting/misleading API consumers.

Suggested change

// Process represents the service that resulted in the creation of a span.

message Process {

// service_name represents the name of the service that resulted in the creation of a span.

string service_name = 1;

// tags describe the metadata about the service, such as host, IP address, environment etc.

// Process represents the process (and associated service) that emitted a span, including

// its logical service name and process-level tags.

message Process {

// service_name represents the logical name of the service for the process that emitted the span.

string service_name = 1;

// tags describe process-level metadata for the emitting process/service, such as host, IP address,

// environment, and other attributes that apply to the process as a whole.

Copilot · 2026-03-04T09:57:03Z

proto/api_v2/model.proto

  ];
+  // operation_name is the name of the operation.
  string operation_name = 3;
+  // References to other spans.


Field doc style is inconsistent with other protos in this repo: many fields use comments that start with the field name (e.g. samplingRate is ... in proto/api_v2/sampling.proto), which improves generated docs. For references, the comment could start with references rather than a generic phrase so it's clearer in generated output.

Suggested change

// References to other spans.

// references are links to other spans.

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-04T10:04:10Z

proto/api_v2/model.proto

@@ -67,85 +76,116 @@ message Log {
  ];
 }

+// SpanRefType describes the relationship between the two spans.
 enum SpanRefType {
  CHILD_OF = 0;
  FOLLOWS_FROM = 1;
 };


PR description says all types/fields are documented, but some newly touched parts are still missing field/enum-value documentation (e.g., Log.timestamp, Log.fields, and the ValueType/SpanRefType enum values). Consider adding brief comments for these to fully satisfy the TODO/PR goal.

Copilot · 2026-03-04T10:04:11Z

proto/api_v2/model.proto

+  // process represents the process which emitted the span.
  Process process = 10;
+  // Identifier of the process that emits the span.
  string process_id = 11 [
    (gogoproto.customname) = "ProcessID"
  ];
+  // Warnings generated during span creation.
  repeated string warnings = 12;


The new comments on Span.process and Span.process_id don’t explain how they relate to Batch.process and Trace.process_map (there’s an existing note above Batch that span.Process takes priority). To avoid misleading API docs, clarify whether Span.process is optional and when consumers should use process_id to resolve a process definition from Trace.process_map.

Copilot · 2026-03-04T10:04:11Z

proto/api_v2/model.proto

+    // process_id is a unique identifier for each process in the trace.
+    string process_id = 1 [
        (gogoproto.customname) = "ProcessID"
-      ];
-      Process process = 2 [
+    ];
+    // process represents process definition along with service name and tags.
+    Process process = 2 [
        (gogoproto.nullable) = false
-      ];
+    ];


Indentation inside Trace.ProcessMapping is inconsistent with the rest of this proto (option lines under other fields are aligned with two extra spaces, but here they’re indented further). Please align the option indentation/closing bracket formatting to match surrounding fields for readability and to minimize noisy diffs in future formatting runs.

Copilot · 2026-03-04T10:04:11Z

proto/api_v2/model.proto

 // their own instances of Process, with span.Process taking priority
 // over batch.Process.
+
+// Batch represents the group of spans sent to Jaeger over a wire.


Minor grammar: “sent to Jaeger over a wire” reads awkwardly; “over the wire” (or “on the wire”) is the standard phrasing in the rest of the repo/industry docs.

Suggested change

// Batch represents the group of spans sent to Jaeger over a wire.

// Batch represents the group of spans sent to Jaeger over the wire.

chore:Document all the types and fields of model.proto

c41aa44

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot AI review requested due to automatic review settings February 28, 2026 11:28

Merge branch 'main' into Document_all_branches_and_fields

35a4183

Copilot started reviewing on behalf of chethanm99 February 28, 2026 11:29 View session

Copilot AI reviewed Feb 28, 2026

View reviewed changes

chore: Updated the comments with typos

2674952

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

chethanm99 requested a review from Copilot March 3, 2026 07:42

Copilot started reviewing on behalf of chethanm99 March 3, 2026 07:42 View session

Copilot AI reviewed Mar 3, 2026

View reviewed changes

chethanm99 changed the title ~~chore:Document all the types and fields of model.proto~~ chore : Document all the types and fields of model.proto Mar 4, 2026

Make comment changes

7fa6ac3

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

chethanm99 requested a review from Copilot March 4, 2026 09:01

Copilot started reviewing on behalf of chethanm99 March 4, 2026 09:01 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

Make typo changes

b7e5bc5

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

chethanm99 requested a review from Copilot March 4, 2026 09:26

Copilot started reviewing on behalf of chethanm99 March 4, 2026 09:26 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

Make minor typo changes

c655248

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

chethanm99 requested a review from Copilot March 4, 2026 09:31

Copilot started reviewing on behalf of chethanm99 March 4, 2026 09:32 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

Make typo changes

c315e33

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

chethanm99 requested a review from Copilot March 4, 2026 09:38

Copilot started reviewing on behalf of chethanm99 March 4, 2026 09:38 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

Make small typo changes

24095ac

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

chethanm99 requested a review from Copilot March 4, 2026 09:54

Copilot started reviewing on behalf of chethanm99 March 4, 2026 09:54 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

chethanm99 added 2 commits March 4, 2026 15:29

Fix typos and improve comments

a22ba07

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Fix typos and improve comments

361afbb

Signed-off-by: chethanm99 <chethanm1399@gmail.com>

Copilot AI review requested due to automatic review settings March 4, 2026 10:00

Copilot started reviewing on behalf of chethanm99 March 4, 2026 10:00 View session

Copilot AI reviewed Mar 4, 2026

View reviewed changes

chethanm99 closed this Mar 6, 2026

		//ValueType describes the type of value stored in a key-value pair.
		enum ValueType {

	//lifecycle events that occured during the execution of the span in key-value format.
	//lifecycle events that occurred during the execution of the span in key-value format.

	//Process represents the service that resuted in the creation of span.
	//Process represents the service that resulted in the creation of span.

	//span_id indentifies the ID of the span.
	//span_id identifies the ID of the span.

	//It represents the name of the operation.
	// operation_name is the name of the operation.

		//SpanRef describes the reference from one span to another, it
		//establishes relationship between the spans.

	//call_count represents the number of calls between the two services.
	// call_count represents the number of calls between the two services.

	// duration represents how long did the span run.
	// duration represents how long the span ran.

	// Trace represents the collection of spans with same trace ID.
	// Trace represents the collection of spans with the same trace ID.

	// process_map represents the mapping of process identifiers to thier process definitons.
	// process_map represents the mapping of process identifiers to their process definitions.

	// process_id is a unique identifier to each process in the trace.
	// process_id is a unique identifier for each process in the trace.

	// ProcessMapping represents the name and tags of the service.
	// ProcessMapping represents a single mapping entry from a process_id
	// to its Process definition (including service name and tags).

	// Span represents the single operation performed within the trace.
	// Span represents a single operation performed within the trace.

		// Log is a time-stamped event which captures the incidents such as errors,
		// lifecycle events that occurred during the execution of the span in key-value format.

	// trace_id identifies ID of the trace, all the spans within it share the same trace_id.
	// trace_id is the ID of the trace; all the spans within it share the same trace_id.

	// Warnings generation during span creation.
	// Warnings generated during span creation.

	// References to other spans.
	// references are links to other spans.

	// Batch represents the group of spans sent to Jaeger over a wire.
	// Batch represents the group of spans sent to Jaeger over the wire.

Conversation

chethanm99 commented Feb 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description of the changes

Checklist

AI Usage in this PR (choose one)

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 4, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 4, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 4, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 4, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 4, 2026

chethanm99 commented Feb 28, 2026 •

edited

Loading