Monitoring Cisco UCCX

Attached (hopefully attached) is a Zip with the datasources I use.   Some were from LM Dev's and others I wrote.    

EDIT:::: Here's a link to download it since I can't attach ZIPs here.     https://1drv.ms/u/s!Ak3nIowLj9hMhewrrVqpjGeyrnph_g?e=16ZKXc

FYI, I use a system.category of "CiscoUCCX" for all my UCCX Devices to make sure they get these datasources applied.    I don't have a propertysource that gets this information automatically and set that property.     Use these at your own risk and tweak the thresholds to make it work in your environment.   

·         Cisco_UCCX_AgentStats - This is supposed to show the AgentStats but sometimes doesn’t work.

·         Cisco_UCCX_Applications – This will get a list of applications installed on UCCX and let you know if they are enabled or not.

·         Cisco_UCCX_Campaigns – same as applications but pulls in Campaigns.

·         Cisco_UCCX_DBPurgeConfigurationStatus - Monitors last database purge status.

·         Cisco_UCCX_Processes – Monitors UCCX processes running.

·         Cisco_UCCX_Reporting_Engine_Stats – This one I’ve had issues trying to query.   UCCX AXL interface throws some weird errors with SSL and issues with DNS names vs. IPs.   

·         Cisco_UCCX_Service_Status – Monitors service status.

·         Cisco_UCCX_System_Stats – Monitors system stats and performance.

·         Default_UCCX_Properties – We use this to make sure the device is setup with all the right properties to make these other Datasources work correctly.   It makes sure SSH creds are there and the UCCX logins for the AXL interface are there and work.   We also use this to help us know that the creds we have WORK and if a password change happens, it alarms and lets us know so we can adjust monitoring and keep everything working.

·         UCCX_Backup_Status – This monitors the backup status using SSH creds.    Tweak the thresholds is your jobs are not daily OR take more than 24 hours to run.

·         UCCX_Primary_Node – This monitors the Primary node status.  We’ve had issues where primary node failed over and never failed back causing issues within the cluster.