Cisco APIC Monitoring

Last updated on 16 August, 2022

The Cisco Application Policy Infrastructure Controller (Cisco APIC) is the main architectural component of the Cisco ACI solution. It is the unified point of automation and management for the Cisco ACI fabric, policy enforcement, and health monitoring.

Using LogicMonitor’s Cisco APIC package, you can monitor the controller’s compute hypervisor status, fabric pod/node health, interface performance, system CPU, and more.

Compatibility

​​LogicMonitor’s Cisco APIC package is compatible with:

  • Release 2.2(1) – 4.1(1)

As Cisco releases newer versions of APIC, LogicMonitor will test and extend coverage as necessary.

Setup Requirements

  • Import the LogicMonitor_Collector_Snippets DataSource to ensure that your collector supports the code in this monitoring suite, or update to EA Collector 32.100 or later.

Import LogicModules

  1. Import the LogicMonitor_Collector_Snippets DataSource to ensure that your collector supports the code in this monitoring suite, or update to EA Collector 32.100 or later.
  2. Import all Cisco APIC LogicModules, which are listed in the LogicModules in Package section of this support article.

Add Devices Into Monitoring

  1. Add your Cisco APIC controller(s) into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Credentials

LogicMonitor must provide the appropriate credentials in order to successfully access the Cisco APIC REST API. These credentials must belong to an API user account that has been assigned the following minimum permissions:

RoleDescription
Read-onlySee the Cisco APIC REST API Configuration Guide.

After you create the REST API user account, set the following properties on the Cisco APIC resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

PropertyValue
apic.api.userCisco APIC REST API username.
apic.api.passCisco APIC REST API password.
apic.api.portCisco APIC REST API port. If this property is not defined, defaults to 443.

LogicModules in Package

​LogicMonitor’s package for Cisco APIC contains the following LogicModules. Please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Display NameTypeDescription
addCategory_Cisco_APICPropertySourceUses the procEntity class (which should always return if processes are running on the system) to judge if a connection to Cisco APIC is possible and add the corresponding system category.
Cisco APIC TenantsDataSourceObtains information about tenants via the APIC API.
Cisco APIC StorageDataSourceObtains storage information via the APIC API.
Cisco APIC Processes ContainersDataSourceStatus information for process containers running on the APIC.
Cisco APIC MemoryDataSourceSystem Memory information from the APIC.
Cisco APIC InterfacesDataSourceObtains information about interface performance via the APIC API.
Cisco APIC HypervisorDataSourceStatus information for compute hypervisor deployed within the fabric.
Cisco APIC FansDataSourceSystem fan information from the APIC.
Cisco APIC Fabric Pod HealthDataSourceObtains information about fabric pod health via the APIC API.
Cisco APIC Fabric Node HealthDataSourceObtains information about fabric node health via the APIC API.
Cisco APIC Endpoint GroupsDataSourceObtains information about endpoint groups via the APIC API.
Cisco APIC Cluster StatusDataSourceObtains information about the cluster via the APIC API.
Cisco APIC CapacityDataSourceObtains information about APIC capacity via the APIC API.
Cisco APIC CPUDataSourceSystem CPU information from the APIC.
Cisco APIC Bridge DomainsDataSourceObtains information about bridge domains via the APIC API.
Cisco APIC BGPDataSourceObtains information about BGP peerings via the APIC API.
Cisco APIC Application ProfilesDataSourceObtains information about the application profiles via the APIC API.

When setting static datapoint thresholds on the various metrics tracked by this integration package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

In This Article