Document updated on Oct 24, 2022
Since | v1.1 |
---|---|
Namespace | telemetry/opencensus |
Log prefix | [SERVICE: Opencensus] |
Scope | service |
Source | krakendio/krakend-opencensus |
The ocagent
exporter sends OpenCensus Stats and Traces to the OpenCensus Agent, instead of pushing data to backends’ exporters.
For instance, you can enable ocagent to upload data to the OpenCensus Agent, and from there, the agent is simply scraped by a Prometheus.
You can integrate the OpenCensus Agent with Azure Monitor, Jaeger, or Prometheus to name a few examples.
Enabling it only requires you to add the ocagent
exporter in the opencensus module.
The following configuration snippet sends the data:
{
"extra_config": {
"telemetry/opencensus": {
"sample_rate": 100,
"reporting_period": 0,
"exporters": {
"ocagent": {
"address": "collector",
"service_name": "krakend",
"reconnection": "2s",
"insecure": false,
"enable_compression": true,
"headers": {
"header1": "value1"
}
}
}
}
}
As with all OpenCensus exporters, you can add optional settings in the telemetry/opencensus
level:
"telemetry/opencensus"
| 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 ocagent
entry with the following properties:
"telemetry/opencensus": { "exporters":{} }
| Exporting metrics, logs, and events to the OpenCensus Agent.
|
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.