Teams Chat Availability

Summary

This monitor uses the Graph API to retrieve the ID of a Team which was created before by metric 70031. Then it will run the "Get Team" API call to retrieve details of the Team. If this fails, metrics value changes.

An alert triggers on an error state when there is a Teams outage.

Requirement: A Team to check must exist. This is created by running metric 70031 or waiting for the monitor, 'Monitor Teams Chat - Test Light', to create a Team.

Teams health score algorithm:

• A previously created team to check does not exist: allocate a metric value of 5. Availability state is set to warning.

• Team is present and details received : allocate a metric value of 10. Availability state is set to healthy.

• Password of user is incorrect: allocate a metric value of 3. Availability state is set to warning. An alert is not sent.

• An error occurred while retrieving a token for Teams: allocate a metric value of 4. Availability state is set to warning. An alert is not sent.

• The 'Get Team' endpoint provides an exception or is unavailable: allocate metric value 0. Availability state is set to critical. An alert is sent.

Monitor implementation:

• This is a Minimum Monitor.

• HEALTY: Value > 5

• WARNING: 5 >= Value > 2

• CRITICAL: Value < 2

Configuration

Requires Microsoft Graph API permission 'Group.ReadWrite.All' for calls to 'Get team'.

Causes

Please see the Alert Context or State Change tab for details.

Resolutions

Depends on the cause of the issue, which can be manifold. Please refer to the below section for "additional information".

Additional

Test credentials configuration

Graph API 'Get Team' call

This monitor depends on metric 70031.

External

For more information on NiCE Management Packs for Microsoft System Center Operations Manager visit www.nice.de