Skip to content

Trace Data Collection

Guance's trace data collection currently supports collectors using the Opentracing protocol. After enabling the trace data reception service in DataKit, by completing the instrumentation of the collectors in the code, DataKit will automatically complete the data format conversion and collection, and finally report it to Guance.

Data Collection

DataKit currently supports collecting DDTrace, Apache Jaeger, OpenTelemetry, Skywalking, Zipkin and other third-party Tracing data.

Collection Prerequisites

  1. Install DataKit;

  2. Configure all relevant collectors for trace data collection.

Collector Configuration

DDTrace

OpenTelemetry

Pinpoint

Field Description

DataKit will convert the reported data into Guance trace data format according to different collectors while preserving labels and Metrics. Below is a description of commonly used fields:

Field Name Description
host Hostname, default global tag.
source The source of the trace; if collected via Zipkin, this value is zipkin, if via Jaeger, this value is jaeger, and so on.
service The name of the service; it is recommended that users specify the name of the business system generating this trace data via this tag.
parent_id The ID of the previous span.
operation The operation name of the current span, which can also be understood as the Span name.
span_id The unique ID of the current span.
trace_id Represents the unique ID of the current trace.
span_type Type of Span, currently supports: entry, local, exit, unknow.
  • entry span indicates a span created when entering a service, i.e., the endpoint where the service provides calls to other services; most spans should be entry spans. Only spans of type entry represent an independent request.
  • local span indicates that the span has no relation to remote calls, it is created during local method calls, such as an ordinary Java method.
  • exit span indicates a span created when leaving a service, such as when initiating a remote call or when a message queue generates a message.
  • unknow span indicates an unknown Span.
    		•
    endpoint The target address of the request, the network address used by the client to access the target service, e.g., 127.0.0.1:8080, default: null.
    message The raw data collected before the trace transformation.
    duration The duration of the current trace span.
    status The status of the trace: info: hint, warning: warning, error: error, critical: severe, ok: success.
    env The environment to which the trace belongs, for example, dev can indicate the development environment, prod can indicate the production environment, and users can customize it.

    For more field lists, refer to DataKit Tracing Data Structure.

    Feedback

    Is this page helpful? ×