News KrakenD CE 2.11.2 and EE 2.11.3 (bugfixing) released

Enterprise Documentation

You are viewing a previous version of KrakenD Enterprise Edition (v2.1), go to the latest version

Document updated on Oct 24, 2022

Exporting traces to Jaeger

Jaeger is an open source, end-to-end distributed tracing system that allows you to monitor and troubleshoot transactions in complex distributed systems.

The Opencensus exporter allows you export data to Jaeger. Enabling it only requires you to add the jaeger exporter in the opencensus module.

The following configuration snippet sends data to your Jaeger:

{
  "extra_config":{
    "telemetry/opencensus": {
      "sample_rate": 100,
      "reporting_period": 0,
      "exporters": {
        "jaeger": {
          "endpoint": "http://192.168.99.100:14268/api/traces",
          "service_name":"krakend",
          "buffer_max_count": 1000
        }
      }
    }
  }
}

As with all OpenCensus exporters, you can add optional settings in the telemetry/opencensus level:

Fields of "telemetry/opencensus"
* required fields

enabled_layers
Lets you specify what data you want to export. All layers are enabled by default unless you declare this section.
backend boolean
Reports the activity between KrakenD and your services
Defaults to false
pipe boolean
Reports the activity at the beginning of the proxy layer. It gives a more detailed view of the internals of the pipe between end-users and KrakenD, having into account merging of different backends.
Defaults to false
router boolean
Reports the activity between end-users and KrakenD
Defaults to false
reporting_period integer
The number of seconds passing between reports. If duration is less than or equal to zero, it enables the default behavior of each exporter.
Defaults to 0
sample_rate integer
A number between 0 (no requests at all) and 100 (all requests) representing the percentage of sampled requests you want to send to the exporter. Sampling the 100% of the requests is generally discouraged when the relationship between traffic and dedicated resources is sparse.
Defaults to 0
Schema: https://www.krakend.io/schema/v2.1/telemetry/opencensus.json

Then, the exporters key must contain an jaeger entry with the following properties:

Fields of "telemetry/opencensus": { "exporters":{} }
* required fields

jaeger object
buffer_max_count integer
Total number of traces to buffer in memory
endpoint * string
The full URL including port indicating where your Jaeger is, e.g., http://jaeger:14268/api/traces
Example: "http://192.168.99.100:14268/api/traces"
service_name * string
The service name registered in Jaeger
Example: "krakend"
Schema: https://www.krakend.io/schema/v2.1/telemetry/opencensus.json

Unresolved issues?

The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.

See all support channels