Call Data Connector Health

Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_CALLDATACONNECTORTELEMETRY_PROCESSING_FAILURE (UnitMonitor)

Knowledge Base article:

Summary

Number of call data telemetry events that failed at the Call Data Telemetry Endpoint

Causes

Encountered error while call data events were being processed.

Resolutions

If the problem persists, notify your organization's support team with the relevant details.

Element properties:

Target

Microsoft.LS.2019.Component.Registrar

Parent Monitor

System.Health.PerformanceState

Category

PerformanceHealth

Enabled

True

Alert Generate

True

Alert Severity

Error

Alert Priority

High

Alert Auto Resolve

True

Monitor Type

Microsoft.LS.2019.Performance.Double.ConsecutiveThresholdMonitor

Remotable

True

Accessibility

Public

Alert Message

[Skype] Number of call data telemetry events that failed at the Call Data Telemetry Endpoint

Perf Object Name:
Perf Counter Name: {0}
Perf Counter Value: {1}
Error Threshold: 10
Warning Threshold: 5
Consecutive Samples Repeat Count: 2
Single instance perf counter
Please see the 'Product Knowledge' and the 'Alert Context' tab on Alert Properties view for more information.

RunAs

Default

Source Code:

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

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Alert_Number_of_call_data_telemetry_events_that_failed_at_the_Call_Data_Telemetry_Endpoint">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>High</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

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

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

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_CALLDATACONNECTORTELEMETRY_PROCESSING_FAILURE_OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error"/>

    <OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_CALLDATACONNECTORTELEMETRY_PROCESSING_FAILURE_UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success"/>

    <OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_CALLDATACONNECTORTELEMETRY_PROCESSING_FAILURE_UnderThresholdOverThreshold" MonitorTypeStateID="UnderThresholdOverThreshold" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

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

    <CounterName>UDC - Number of call data telemetry events that failed at the Call Data Telemetry Endpoint</CounterName>

    <ObjectName>LS:DATACOLLECTION - Call data telemetry Connector in Data Collection Agent</ObjectName>

    <AllInstances>false</AllInstances>

    <Frequency>900</Frequency>

    <IncludeInstances/>

    <ExcludeInstances/>

    <WarningThreshold>5</WarningThreshold>

    <ErrorThreshold>10</ErrorThreshold>

    <NumSamples>2</NumSamples>

  </Configuration>

</UnitMonitor>