Showing results for 
Search instead for 
Did you mean: 

Monitoring Uptime on Diagnostic Portico Cisco UCCE

05 Base Camper

Monitoring Uptime on Diagnostic Portico Cisco UCCE

Hi Team,


I'm looking for help to monitor the uptime on diagnostic portico.
We have been saying issues with service/ process restart and are unable to track it & has been creating issues in the production environment. 

I donot see any option of uptime under 'Device Comp Element Down' 
Do we have any whereclause that helps monitor the uptime.Diag portico uptime.PNGDiag portico uptime2.PNG


Re: Monitoring Uptime on Diagnostic Portico Cisco UCCE

Hi @Arathi_R,

The data source for most of the CCE records is via SNMP and supplied by the CISCO-CONTACT-CENTER-APPS-MIB. None of the tables in this MIB appear to provide any "up-time" metrics for components or component entities unfortunately.

If the data you're looking for is supplied by an alternate source, you could request an enhancement to include that additional information in Prognosis if you're aware of another source that provides this. I couldn't guarantee this would be added into the product as other data sources (for example, CLI) are often-times not as efficient to collect and can cause increased overhead on the target device being queried. If you'd like to pursue this option, you can ask your account manager to submit this on your behalf or, if you submit the request initially via a support case, we can direct the request to your account manager on your behalf.

Another option for tracking the availability of these entities, at least from a Prognosis perspective, would be to create a pair of threshold conditions as an Availability pair. I've added a pair of Availability destinations to a modified UCCE_Device threshold so you can get an idea of what this looks like. This was created using Prognosis 12.0, but you should be able to open it using an 11.9 GUI (possibly earlier).

This is a screen shot of the new condition I added to detect when the entity is "up" based on what Prognosis sees (you can also see the corresponding "down" destination in the existing condition just above it):


You may need to refine this (the SubID1 and SubID2 values for example) as I just added in what I thought would make sense, but hopefully this will help you achive what you need!



Scott Clement