community.general.opentelemetry – Create distributed traces with OpenTelemetry
Note
This plugin is part of the community.general collection (version 3.8.3).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.general
.
To use it in a playbook, specify: community.general.opentelemetry
.
New in version 3.7.0: of community.general
Synopsis
This callback creates distributed traces for each Ansible task with OpenTelemetry.
You can configure the OpenTelemetry exporter and SDK with environment variables.
See https://opentelemetry-python.readthedocs.io/en/latest/exporter/otlp/otlp.html.
Requirements
The below requirements are needed on the local controller node that executes this callback.
opentelemetry-api (Python library)
opentelemetry-exporter-otlp (Python library)
opentelemetry-sdk (Python library)
Parameters
Parameter |
Comments |
---|---|
Whether to enable this callback only if the given environment variable exists and it is set to This is handy when you use Configuration as Code and want to send distributed traces if running in the CI rather when running Ansible locally. For such, it evaluates the given enable_from_environment value as environment variable and if set to true this plugin will be enabled. Configuration:
|
|
Hide the arguments for a task. Choices:
Configuration:
|
|
The service name resource attribute. Default: “ansible” Configuration:
|
|
The W3C Trace Context header traceparent. Default: “None” Configuration:
|
Examples
examples: |
Enable the plugin in ansible.cfg:
[defaults]
callbacks_enabled = community.general.opentelemetry
Set the environment variable:
export OTEL_EXPORTER_OTLP_ENDPOINT=<your endpoint (OTLP/HTTP)>
export OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer your_otel_token"
export OTEL_SERVICE_NAME=your_service_name
Authors
Victor Martinez (@v1v) <VictorMartinezRubio@gmail.com>