This check monitors Flux through the Datadog Agent. Flux is a set of continuous and progressive delivery solutions for Kubernetes that is open and extensible.
Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.
Starting from Agent release 7.51.0, the Fluxcd check is included in the Datadog Agent package. No additional installation is needed on your server.
For older versions of the Agent, use these steps to install the integration.
This integration supports collecting metrics and logs from the following Flux services:
helm-controllerkustomize-controllernotification-controllersource-controller
You can pick and choose which services you monitor depending on your needs.
This is an example configuration with Kubernetes annotations on your Flux pods. See the sample configuration file for all available configuration options.
apiVersion: v1
kind: Pod
metadata:
name: '<POD_NAME>'
annotations:
ad.datadoghq.com/manager.checks: |-
{
"fluxcd": {
"instances": [
{
"openmetrics_endpoint": "http://%%host%%:8080/metrics"
}
]
}
}
# (...)
spec:
containers:
- name: 'manager'
# (...)Available for Agent versions >6.0
Flux logs can be collected from the different Flux pods through Kubernetes. Collecting logs is disabled by default in the Datadog Agent. To enable it, see Kubernetes Log Collection.
See the Autodiscovery Integration Templates for guidance on applying the parameters below.
| Parameter | Value |
|---|---|
<LOG_CONFIG> |
{"source": "fluxcd", "service": "<SERVICE_NAME>"} |
Run the Agent's status subcommand and look for fluxcd under the Checks section.
See metadata.csv for a list of metrics provided by this integration.
The fluxcd integration does not include any events.
See service_checks.json for a list of service checks provided by this integration.
Need help? Contact Datadog support.
Additional helpful documentation, links, and articles: