Device Inventory

All target inventory is maintained in the enterprise wxcdi-inventory-files repository and organized by device family and region.

An inventory entry means that a target is intended to be in scope. Confirm Prometheus discovery, scrape status, or recent Splunk data before using it as proof of live monitoring.

Repository Structure

Path	Purpose
inventory/<region>/<vos-type>/	CUCM, CUC, CER, IM&P, and Expressway Prometheus targets
<device>-inventory/<region>/	Network, security, compute, Linux, Windows, ISE, storage, and utility targets
config/devices.yaml	Device-family to node-role mapping
config/regions.yaml	Data-center to region mapping
syslog-ng-output/	Generated syslog enrichment metadata and hosts cache
snmptrap-output/	Consolidated SNMP-trap inventory metadata
sftp-output/	CUCM publisher tenant metadata for CDR/CMR ingestion

The configured regions are us, apac, emea, and uae. Device support differs by family; an empty or missing regional folder should not be interpreted as a collection failure without checking the source inventory.

Inventory Format

Prometheus target files use YAML:

- targets:
    - <management_address>
  labels:
    device_type: <device_family>
    node_type: <device_role>
    region: <region>
    data_center: <data_center>
    device_name: <device_name>
    ip_address: <management_address>

Customer-scoped targets can also include customer_name, customer_id, and tenant. Do not copy real customer records, addresses, or credentials into this documentation.

Updating Inventory

flowchart TD
    A[Authoritative Source Inventory] --> B[Run Device Generator]
    B --> C[Prometheus Target Files]
    B --> D[Syslog Metadata]
    B --> E[SNMP Trap Metadata]
    B --> F[DNS Hosts Cache]
    C --> G[Pull Request Review]
    D --> G
    E --> G
    F --> G
    G --> H[Merge to Main]
    H --> I[Runtime Sync and Discovery]
    I --> J[Verify Metrics Logs and Traps]

1. Update the authoritative source inventory and start from the latest main branch.
2. Run the device-family generator documented in the inventory repository README.
3. Regenerate affected syslog metadata, consolidated trap metadata, and the hosts cache.
4. For CUCM publisher changes, also regenerate the SFTP tenant maps.
5. Check whether the exporter has a second target list in wxcdi-kubed-configs; UCS and vCenter are specifically called out by the inventory runbook.
6. Review the diff for only the intended targets and generated artifacts.
7. Merge through pull request, then verify target discovery and telemetry freshness.

ACI, MSW, vCenter, UCS standalone, SAN, and selected FMC/UCSM records include manual-maintenance steps. Follow the repository README rather than assuming every folder is fully generated.

Per-Device Inventory

Device	Repository Link
CUCM	inventory
CUC	inventory
CER	inventory
IMP	inventory
Expressway	inventory
SBC / CUBE	csr-cube-inventory
ACI	aci-inventory
HyperFlex	No current inventory link is recorded in the audit
UCS	ucs-sa-inventory / ucsm-inventory
vCenter	vcenter-inventory
CSR	csr-cube-inventory
ASA	asa-inventory
FMC	ftd-firepower-inventory
FTD	ftd-firepower-inventory
MSW	msw-inventory
Nexus	nexus9k-inventory