Community Documentation
You are viewing a previous version of KrakenD Community Edition (v2.1)
, go to the latest version
Exporting traces to Jaeger
Document updated on Oct 24, 2022
About this feature
| Since | v0.5 |
|---|---|
| Namespace | telemetry/opencensus |
| Log prefix | [SERVICE: Opencensus] |
| Scope | service |
| Source | krakend/krakend-opencensus |
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
| Lets you specify what data you want to export. All layers are enabled by default unless you declare this section.
| ||||||
| 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 | ||||||
| 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 |
Then, the exporters key must contain an jaeger entry with the following properties:
Fields of
"telemetry/opencensus": { "exporters":{} }
* required fields
|
|
