This monitor represents the availability of User Data Conferencing as monitored by Synthetic Transactions.
Cmdlet Executed: Test-CSDataConference
For more information on this cmdlet, open a Skype for Business Server 2015 Management Shell window and type:
Get-help Test-CSDataConference -detailed
To configure users for Synthetic Transactions to execute periodically please use the New-CSwatcherNodeConfiguration cmdlet.
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.
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.
| Target | Microsoft.LS.2015.PoolWatcher.DataConference |
| Parent Monitor | System.Health.PerformanceState |
| Category | PerformanceHealth |
| Enabled | True |
| Alert Generate | False |
| Alert Auto Resolve | True |
| Monitor Type | Microsoft.LS.2015.MonitorType.Health.ST.Perf |
| Remotable | True |
| Accessibility | Public |
| RunAs | Default |
Home
<UnitMonitor ID="Microsoft.LS.2015.Monitoring.UnitMonitor.SyntheticTransaction.DataConference.Perf" Accessibility="Public" Enabled="true" Target="Microsoft.LS.2015.PoolWatcher.DataConference" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2015.MonitorType.Health.ST.Perf" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<OperationalStates>
<OperationalState ID="SuccessState" MonitorTypeStateID="Success" HealthState="Success"/>
<OperationalState ID="WarningState" MonitorTypeStateID="Warning" HealthState="Warning"/>
</OperationalStates>
<Configuration>
<TargetFqdn>$Target/Host/Property[Type="Microsoft.LS.2015.PoolWatcher"]/TargetFqdn$</TargetFqdn>
<TestId>DataConference</TestId>
<InstanceId/>
<ObjectName>DataConference Performance</ObjectName>
<CounterName>"DataConference Performance Latency (sec)"</CounterName>
<InstanceName>[$Target/Host/Property[Type="Microsoft.LS.2015.PoolWatcher"]/TargetFqdn$][]</InstanceName>
<ExpectedLatencyThresholdSeconds>90.0</ExpectedLatencyThresholdSeconds>
</Configuration>
</UnitMonitor>