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 ability to monitor devices via Network Devices Monitoring
The Cisco ACI check is packaged with the Agent, so simply install the Agent on a server within your network.
To configure this check for an Agent running on a host:
-
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: http://localhost ## @param username - string - required ## Authentication can use either a user auth or a certificate. ## If using the user auth, enter the `username` and `pwd` configuration. # username: datadog ## @param pwd - string - required ## Authentication can use either a user auth or a certificate. ## If using the user auth, enter the `username` and `pwd` configuration. # pwd: <PWD> ## @param tenant - list of strings - optional ## List of tenants to collect metrics data from. # # tenant: # - <TENANT_1> # - <TENANT_2> ## @param send_ndm_metadata - boolean - optional - default: false ## Set to `true` to enable Network Device Monitoring metadata (for devices and interfaces) to be sent. # # send_ndm_metadata: false
NOTE: Be sure to specify any tenants for the integration to collect metrics on applications, EPG, etc.
-
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> |
cisco_aci |
<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.
Specific supported vendor profiles for this integration can be found on the network vendors page.
See metadata.csv for a list of metrics provided by this integration.
The Cisco ACI check sends tenant faults as events.
See service_checks.json for a list of service checks provided by this integration.
If you are missing cisco_aci.tenant.*
metrics, you can run the test/cisco_aci_query.py
script to manually query the tenant endpoint.
Modify the apic_url
, apic_username
, and apic_password
to your configuration information, and input the tenant URL for the apic_url
.
Verify that the output you get from cURLing the endpoint matches any of the metrics collected in datadog_checks/cisco_aci/aci_metrics.py
. If none of the statistics match, this means that the endpoint is not emitting any statistics that the integration can collect.
Because this check queries all the tenants, apps, and endpoints listed before returning metrics, there may be high execution times coming from this integration.
cisco_aci (2.2.0)
-----------------
Instance ID: cisco_aci:d3a2958f66f46212 [OK]
Configuration Source: file:/etc/datadog-agent/conf.d/cisco_aci.d/conf.yaml
Total Runs: 1
Metric Samples: Last Run: 678, Total: 678
Events: Last Run: 0, Total: 0
Service Checks: Last Run: 1, Total: 1
Average Execution Time : 28m20.95s
Last Execution Date : 2023-01-04 15:58:04 CST / 2023-01-04 21:58:04 UTC (1672869484000)
Last Successful Execution Date : 2023-01-04 15:58:04 CST / 2023-01-04 21:58:04 UTC (1672869484000)
Need help? Contact Datadog support.