Home
  •  

Call Reliability Collection Rule (Conferencing).

Microsoft.LS.2010.Service.MonitoringServer.CDR.Conf.Rule.Collect (Rule)

This rule queries the Call reliability database and raises an event per bad diagnostic Id for Conference calls.

Knowledge Base article:

Summary

When an audio conference call fails, this failure is reported to the Monitoring Server database (Call Detail Records database) along with a specific diagnosis code indicating the reason for the failure. This rule collects this data periodically from the CDR database.

Here are the available parameters that can be configured on this collection rule: To view current values or change behavior, please look at these overrideable parameters.

Item

Description

Type

Frequency

How often does this rule execute and query Monitoring Server data (CDR database) for Conferencing call failures?

Integer.

Number of Seconds

MinutesToQuery

On each execution of this rule, query failures for the last “x” minutes.

Integer.

Number of Minutes

MinUsersAffected

Minimum number of users that should be impacted before this Diagnosis failure is raised as an “Alert”

Integer.

AlertThresholdPercentage

If Call failures with a particular diagnosis code exceed “x%” of total completed calls, then generate an alert.

Decimal, 0.00% to 100.00%

Element properties:

TargetMicrosoft.LS.2010.WatcherNode.CDR
CategoryPerformanceCollection
EnabledTrue
Alert GenerateFalse
RemotableTrue

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.LS.2010.Service.MonitoringServer.CDR.DSModuleType Default
PerfMapper ConditionDetection System.Performance.DataGenericMapper Default
WriteToDB WriteAction Microsoft.SystemCenter.CollectPerformanceData Default

Source Code:

<Rule ID="Microsoft.LS.2010.Service.MonitoringServer.CDR.Conf.Rule.Collect" Enabled="true" Target="Microsoft.LS.2010.WatcherNode.CDR" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>PerformanceCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Microsoft.LS.2010.Service.MonitoringServer.CDR.DSModuleType">

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

      <Frequency>300</Frequency>

      <MinutesToQuery>60</MinutesToQuery>

      <AlertThresholdPercentage>1.2</AlertThresholdPercentage>

      <MinUsersImpacted>2</MinUsersImpacted>

      <SQLInstance>$Target/Property[Type="Microsoft.LS.2010.WatcherNode.CDR"]/SQLInstance$</SQLInstance>

      <ReportingServiceUrl>$Target/Property[Type="Microsoft.LS.2010.WatcherNode.CDR"]/ReportingServiceUrl$</ReportingServiceUrl>

      <ScriptName>Microsoft Lync Server 2010 CDR Conference Execution Report</ScriptName>

      <ScriptFileName>CdrConfDSModuleType.ps1</ScriptFileName>

      <SprocName>GetSCOMConferencingAlertData</SprocName>

      <ExtensionForReportUrl>&amp;Filter_ActivityType=1&amp;Filter_Category=2</ExtensionForReportUrl>

      <TimeoutSeconds>60</TimeoutSeconds>

      <EventId>327</EventId>

      <CDRRuleEventId>3122</CDRRuleEventId>

    </DataSource>

  </DataSources>

  <ConditionDetection ID="PerfMapper" TypeID="SystemPerf!System.Performance.DataGenericMapper">

    <ObjectName>CDR Object</ObjectName>

    <CounterName>CDR Counter</CounterName>

    <InstanceName>CDR Instance</InstanceName>

    <Value>1.0</Value>

  </ConditionDetection>

  <WriteActions>

    <WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData"/>

  </WriteActions>

</Rule>