Follow the instructions below to install and configure this check for an Agent running on a host.

1. Edit the velero.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Velero performance data. See the sample velero.d/conf.yaml for all available configuration options.

2. Restart the Agent.

See the Autodiscovery Integration Templates for guidance on configuring this integration in a containerized environment.

Note that two types of pods need to be queried for all metrics to be collected: velero and node-agent Therefore, make sure to update the annotations of the velero deployment as well as the node-agent daemonset.

To collect logs from Velero containers on a host:

1. Collecting logs is disabled by default in the Datadog Agent. Enable it in your datadog.yaml file:

   logs_enabled: true
   

2. Uncomment and edit the logs configuration block in your velero.d/conf.yaml file. For example:

   logs:
     - type: docker
       source: velero
       service: velero
   

To collect logs from a Velero Kubernetes deployment:

1. Collecting logs is disabled by default in the Datadog Agent. To enable it, see Kubernetes Log Collection.

2. Set Log Integrations as pod annotations. This can also be configured with a file, a ConfigMap, or a key-value store. For more information, see the configuration section of Kubernetes Log Collection.