cancel
Showing results for 
Search instead for 
Did you mean: 

MsTeams-CallAlerts thresholds

JohnMcCormack
05 Base Camper

MsTeams-CallAlerts thresholds

Hi,

 

    What is the significance of the MsTeams-CallAlerts alerts ?  The thresholds are generating alerts with a level of 'error' when the queries do not return any rows, but why is this an error ?   E.g. if it queries for sessions and there were no sessions in that time period, and the query did not encounter any issues, it still generates an error alert ?

I would like to know if I can safely disable these thresholds without missing any actual errors that an engineer should investigate ?

Thanks,

John

1 ACCEPTED SOLUTION

Accepted Solutions

Re: MsTeams-CallAlerts thresholds

Hi @JohnMcCormack,

 

These alerts are a warning that there haven't been any rows captured by the Call, Media, Segment or Session gatherers in Prognosis. Under normal circumstances, this might be indicative of a connectivity issue between the gatherer and Microsoft's clould.

If it's normal to have no rows being published at certain times, e.g. outside of normal business hours, one suggest would be to modify the conditions so they only trigger between certain times each day (during business hours).

The existing conditions are already set to trigger after five consecutive occurrences (so after 25 minutes). If it's common to have no rows published for longer periods during the day, then another option would be to increase the 'log after' value. 

If you're not sure what the typical behaviour is, then replaying the MsTeams-Health database (to review the MsTeamsWebServiceStatus record over the course of a week) would help provide some insight into what the "norm" is. That should then help determine how to tune your alerts so you're less likely to receive false alarms.

 

Hopefully this helps!

Regards,

Scott Clement

 

View solution in original post

2 REPLIES 2

Re: MsTeams-CallAlerts thresholds

Hi @JohnMcCormack,

 

These alerts are a warning that there haven't been any rows captured by the Call, Media, Segment or Session gatherers in Prognosis. Under normal circumstances, this might be indicative of a connectivity issue between the gatherer and Microsoft's clould.

If it's normal to have no rows being published at certain times, e.g. outside of normal business hours, one suggest would be to modify the conditions so they only trigger between certain times each day (during business hours).

The existing conditions are already set to trigger after five consecutive occurrences (so after 25 minutes). If it's common to have no rows published for longer periods during the day, then another option would be to increase the 'log after' value. 

If you're not sure what the typical behaviour is, then replaying the MsTeams-Health database (to review the MsTeamsWebServiceStatus record over the course of a week) would help provide some insight into what the "norm" is. That should then help determine how to tune your alerts so you're less likely to receive false alarms.

 

Hopefully this helps!

Regards,

Scott Clement

 

JohnMcCormack
05 Base Camper

Re: MsTeams-CallAlerts thresholds

Ok, thanks Scott, that was helpful.  I'll tune them.