This check monitors ArangoDB through the Datadog Agent. ArangoDB 3.8 and above are supported.
Enable the Datadog-ArangoDB integration to:
- Identify slow queries based on user-defined thresholds.
- Understand the impact of a long request and troubleshoot latency issues.
- Monitor underlying RocksDB memory, disk, and cache limits.
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 to apply these instructions.
The ArangoDB check is included in the Datadog Agent package.
-
Edit the
arangodb.d/conf.yaml
file in theconf.d/
folder at the root of your Agent's configuration directory to start collecting your ArangoDB performance data. See the sample arangodb.d/conf.yaml for all available configuration options.
Run the Agent's status subcommand and look for arangodb
under the Checks section.
See metadata.csv for a list of metrics provided by this check.
Available for Agent versions >6.0
To collect logs from your ArangoDB instance, first make sure that your ArangoDB is configured to output logs to a file.
For example, if using the arangod.conf
file to configure your ArangoDB instance, you should include the following:
# ArangoDB configuration file
#
# Documentation:
# https://www.arangodb.com/docs/stable/administration-configuration.html
#
...
[log]
file = /var/log/arangodb3/arangod.log
...
ArangoDB logs contain many options for log verbosity and output files. Datadog's integration pipeline supports the default conversion pattern.
-
Collecting logs is disabled by default in the Datadog Agent. Enable it in your
datadog.yaml
file:logs_enabled: true
-
Uncomment and edit the logs configuration block in your
arangodb.d/conf.yaml
file:logs: - type: file path: /var/log/arangodb3/arangod.log source: arangodb
The ArangoDB 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.