Situations to watch In CAPM

[Praveen Venkatesan]

Hi All,

 How the situations to watch  report is getting calculated in CAPM , can someone share the calculation method which is used.

[Jeffrey Pinard]

That CABI report does some ODATA calls to the PC odata proxy.

Which an example is:  /odata/api/portmfs?$apply=groupby(ID,%20aggregate(im_Availability%20with%20timetothreshold%20as%20Value,im_Availability%20with%20slope%20as%20Value1,im_Availability%20with%20projection%20as%20Value2,im_Availability%20with%20average%20as%20Value3,im_Availability%20with%20datasetcount%20as%20Value4))&$format=json&resolution=RATE&starttime=1620240731&endtime=1622832731&$expand=device,component&$select=device/Name,component/Name,Value,Value1,Value2,Value3,Value4&threshold=0&prjoffset=0&$filter=((groups/ID%20eq%20615431)%20and%20((Value%20ge%20-0)))&$orderby=Value%20asc&tz=-04:00&$skip=0&$top=10

So reading that, it appears to look at Interfaces in the group specified in CABI.  
It's looking for only interfaces where time to threshold is greater than 0.

It's grabbing Device Name, Interface Name, and...
1. the time it would take/took to reach the threshold of 0 (down) availability
2. the calculated slope of all interface availabilty values (used for projecting)
3. the 30 day projected interface Availability
4. the average im_Availability for the last 30 days using as-polled (5 min) data.

Not sure how CABI is using the data, but appears it may be trying to find interfaces that are close to being down based off projecting via slope and current average over last 30 days.