Audio Video Conferencing Synthetic Transaction Availability Health Monitor

  • ID:  Microsoft.LS.2015.Monitoring.UnitMonitor.SyntheticTransaction.AVConference.Avail
  • Description:  Audio Video Conferencing Synthetic Transaction Availability Health
  • Target:  Audio Video Conference Watcher
  • Enabled:  Yes

Operational States

Name State Description
Audio Video Conferencing Synthetic Transaction Availability Health - SuccessState Success  
Audio Video Conferencing Synthetic Transaction Availability Health - WarningState Warning  
Audio Video Conferencing Synthetic Transaction Availability Health - ErrorState Error  

Alert Details

Monitor State Message Priority Severity Auto Resolution
Audio Video Conferencing Synthetic Transaction Availability Health - ErrorState (Error) [Skype] Audio Video Conferencing Synthetic Transaction failed. High Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This monitor represents the availability of Audio Video Conference availability as monitored by Synthetic Transactions.

Cmdlet Executed: Test-CsAVConference

For more information on this cmdlet, open a Skype for Business Server 2015 Management Shell window and type:

Get-help Test-CsAVConference -detailed

Causes

The following are possible causes for this failure:

  • Configuration errors

  • Server/Component is down for maintenance.

  • Network/connectivity issues between Watcher node (where the ST executes) and the Front-end Pool.

  • Component specific errors.

Resolutions

Configuration errors: Most common issues are: Test user password is invalid or expired, Test users have not been configured correctly for this Pool. Please refer Synthetic Transaction Internal Alerts View for more details

Server/Component is down for Maintenance: Please ensure that you put Synthetic Transactions in maintenance mode before performing server/pool maintenance. To do this, use the Task Start Pool maintenance in the Pools view.

Network/Connectivity issues: Look at Alert Context tab for more details on the exact connectivity error such as DNS resolution errors or Connection Timeout. You can also get more details on Connectivity errors by looking at Port Check Alerts view.

Component specific errors: Look at Alert Context tab for more details on the component specific error. The specific Front-end server (within the load-balanced Front-end Pool) that responded to this execution of the synthetic transaction is listed in the Alert Context along with the Exception Message associated with the failure.

External References
This monitor does not contain any external references.

See Also for Lync Server 2015 Monitoring Management Pack


Downloads for Lync Server 2015 Monitoring Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED