Home
  •  

The latency of calling PIC web service

Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_PICWebServiceCallLatency (UnitMonitor)

Knowledge Base article:

Summary

This counter shows the average time (in seconds) to perform a PIC provision web service call.

Causes

The latency of calling Public provider web service is too high.

Resolutions

Check if Public provider web service is still working well. And notify Skype for Business Server team with the alert detail.

Element properties:

TargetMicrosoft.LS.2015.Component.ProvisionService
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.LS.2015.Performance.Double.ConsecutiveThresholdMonitor
RemotableTrue
AccessibilityPublic
Alert Message
[Skype] This counter shows the average time (in seconds) to perform a PIC provision web service call.
Perf Object Name:
Perf Counter Name: {0}
Perf Counter Value: {1}
Error Threshold: 60
Warning Threshold: 5
Consecutive Samples Repeat Count: 2

Please see the 'Product Knowledge' and the 'Alert Context' tab on Alert Properties view for more information.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_PICWebServiceCallLatency" Accessibility="Public" Enabled="true" Target="Microsoft.LS.2015.Component.ProvisionService" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2015.Performance.Double.ConsecutiveThresholdMonitor" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Alert_This_counter_shows_the_average_time__in_seconds__to_perform_a_PIC_provision_web_service_call.">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/CounterName$</AlertParameter1>

      <AlertParameter2>$Data/Context/SampleValue$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_PICWebServiceCallLatency_OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error"/>

    <OperationalState ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_PICWebServiceCallLatency_UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success"/>

    <OperationalState ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.ProvisionService.Provision_PICWebServiceCallLatency_UnderThresholdOverThreshold" MonitorTypeStateID="UnderThresholdOverThreshold" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

    <ComputerName>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

    <CounterName>- PIC web service latency (sec)</CounterName>

    <ObjectName>LS:Provision - Provision</ObjectName>

    <InstanceName/>

    <AllInstances>true</AllInstances>

    <Frequency>900</Frequency>

    <WarningThreshold>5</WarningThreshold>

    <ErrorThreshold>60</ErrorThreshold>

    <NumSamples>2</NumSamples>

  </Configuration>

</UnitMonitor>