The Cisco ACI Integration lets you:
- Track the state and health of your network
- Track the capacity of your ACI
- Monitor the switches and controllers themselves
The Cisco ACI check is packaged with the Agent, so simply install the Agent on a server within your network.
Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.
-
Edit the
cisco_aci.d/conf.yaml
file, in theconf.d/
folder at the root of your Agent's configuration directory. See the sample cisco_aci.d/conf.yaml for all available configuration options:init_config: instances: ## @param aci_url - string - required ## Url to query to gather metrics. # - aci_url: localhost ## @param username - string - required ## Authentication can use either a user auth or a certificate. ## If using the user auth, enter in this parameter the associated username. # username: datadog ## @param pwd - string - required ## Authentication can use either a user auth or a certificate. ## If using the user auth, enter in this parameter the associated password. # pwd: datadog
-
Restart the Agent to begin sending Cisco ACI metrics to Datadog.
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
Parameter | Value |
---|---|
<INTEGRATION_NAME> |
teamcity |
<INIT_CONFIG> |
blank or {} |
<INSTANCE_CONFIG> |
{"aci_url":"%%host%%", "username":"<USERNAME>", "pwd": "<PASSWORD>"} |
Run the Agent's status
subcommand and look for cisco_aci
under the Checks section.
See metadata.csv for a list of metrics provided by this integration.
The Cisco ACI check sends tenant faults as events.
cisco_aci.can_connect
:
Returns CRITICAL if the Agent cannot connect to the Cisco ACI API to collect metrics, otherwise OK.
Need help? Contact Datadog support.