Cisco CDR Reporting & Analytics | Installation Notes
Alongside the other core lookups in the app, there is one for devices. When it is populated like the other lookups it automatically makes various other fields available for searching, grouping, reporting etc.
For some more details and examples on what you would get out of doing this work, read our Usage docs about Devices
The best way to set it up is with our Supporting App for AXL. This is a separate Splunk app that we sell and it is indeed an extra cost. In a nutshell when you install it and configure it, it allows ad-hoc or scheduled searches to connect to CUCM directly via AXL and pull back a vast range of almost anything you’d care to know about your CUCM.
Read through its installation and setup documentation. Specifically what you’ll end up with at the end of those docs is one scheduled search that runs every night and populates all of the fields in the Devices Lookup.
You can also absolutely populate this lookup manually. Navigate in the app to Settings > Define Devices. There you can download the existing devices.csv (which begins life with only a header row and no content). And after you’ve created a suitable CSV matching those columns exactly, the same page allows you to upload that csv.
More adventurous teams may write their own scripts to connect to Cisco’s AXL API themselves and populate the devices.csv file manually. We don’t mind if you do this at all. (although… we also wont be of that much help debugging it if it fails on you).
There are many ways to deploy, configure and update the Splunk Universal Forwarder. Here we cover a variety of the more advanced ways to handle updating the TA for Cisco CDR Reporting and Analytics.