Document updated on Oct 24, 2022
Since | v0.5 |
---|---|
Namespace | telemetry/opencensus |
Log prefix | [SERVICE: Opencensus] |
Scope | service |
Source | krakendio/krakend-opencensus |
Opencensus can export data to the system logger as another exporter. This is not the standard KrakenD Logging, and you should not enable both.
Enabling it only requires you to add the logger
exporter in the opencensus module.
The following configuration snippet enables the logger:
{
"extra_config":{
"telemetry/opencensus": {
"sample_rate": 100,
"reporting_period": 0,
"exporters": {
"logger": {
"stats": true,
"spans": true
}
}
}
}
As with all OpenCensus exporters, you can add optional settings in the telemetry/opencensus
level:
| 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 |
Schema: https://www.krakend.io/schema/v2.3/telemetry/opencensus.json
* indicates a required field.
Then, the exporters
key must contain an logger
entry with the following properties:
| Opencensus can export data to the system logger as another exporter. Recommended to use telemetry/logging instead.
|
Schema: https://www.krakend.io/schema/v2.3/telemetry/opencensus.json
* indicates a required field.
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.
We use cookies to understand how you use our site and to improve your overall experience. By continuing to use our site, you accept our Privacy Policy. More information