Home
  •  

MECM Site server inbox schedule.box send request backlog Monitor

MECM.SiteServer.SchedulerBacklog.NumberOfSendRequests.PerfThreshold.Monitor (UnitMonitor)

This monitor checks backlog of schedule.box send request on site server. It raises alert if the backlog exceeds the threshold.

Knowledge Base article:

Summary

The total number of queued scheduler send requests has exceeded the standard operational threshold. Large backlogs indicate that information is not being sent through the site hierarchy. If this condition is caused by isolated events such as a large software distribution package being sent to another site, the problem may resolve on its own if there is sufficient processing time. If the condition is caused by repeated events, such as large numbers of clients sending resynchronized inventory, the problem will not be resolved until you fix the root cause. If the queued scheduler send requests count keeps going beyond the threshold, the length of time required to complete site-to-site communication increases. This could result in delays in processing software distribution to child sites or refreshing inventory information about parent sites.

Causes

The scheduler job messages can exceed the threshold because:

The SMS Executive service is stopped or not responding on the site server.

The processing rate of site server scheduler send requests is slower than the incoming rate of send requests that must be created.

The site server has insufficient resources such as CPU, memory, or disk space.

The administrator has sent a large package, or several packages, to one or more child sites.

The sender is not functioning properly between the two sites. This could be due to several reasons, such as network connectivity issues, account access problems, or sender configuration errors.

The administrator has deleted a large number of inventory records, which triggered a large number of inventory resynchronization requests.

A large number of clients has attached to a new site, which triggered a large number of inventory resynchronization requests.

Resolutions

To resolve this issue and lower the number of queued scheduler send requests:

Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific Configuration Manager site.

Verify that SMS Executive service is running on the site server. If it is stopped or not responding, restart the service.

Verify that the sender can connect to the destination site.

Evaluate the processing rates for software distribution to child sites. If the baseline performance for typical package processing is unacceptable, add resources or upgrade to a more powerful computer.

Reduce the size of packages sent to child sites or send them less frequently.

Avoid actions that generate large amounts of traffic between sites, like resynchronized inventory.

Element properties:

TargetMECM.SiteServerRoleBaseClass
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Instance NameSMS Scheduler
Counter NameNumber of Send Requests
Frequency900
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeSystem.Performance.ConsecutiveSamplesThreshold
RemotableTrue
AccessibilityPublic
Alert Message
MECM Site server inbox schedule.box send request backlog alert

Instance {0}
Object {1}
Counter {2}
Has a value {3}
At time {4}
RunAsDefault

Source Code:

<UnitMonitor ID="MECM.SiteServer.SchedulerBacklog.NumberOfSendRequests.PerfThreshold.Monitor" Accessibility="Public" Enabled="true" Target="MECM.SiteServerRoleBaseClass" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Perf!System.Performance.ConsecutiveSamplesThreshold" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="MECM.SiteServer.SchedulerBacklog.NumberOfSendRequests.PerfThreshold.Monitor.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/InstanceName$</AlertParameter1>

      <AlertParameter2>$Data/Context/ObjectName$</AlertParameter2>

      <AlertParameter3>$Data/Context/CounterName$</AlertParameter3>

      <AlertParameter4>$Data/Context/SampleValue$</AlertParameter4>

      <AlertParameter5>$Data/Context/TimeSampled$</AlertParameter5>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="ConditionFalse" MonitorTypeStateID="ConditionFalse" HealthState="Success"/>

    <OperationalState ID="ConditionTrue" MonitorTypeStateID="ConditionTrue" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

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

    <CounterName>Number of Send Requests</CounterName>

    <ObjectName>SMS Scheduler</ObjectName>

    <InstanceName>_Total</InstanceName>

    <AllInstances>false</AllInstances>

    <Frequency>900</Frequency>

    <Threshold>10000</Threshold>

    <Direction>greater</Direction>

    <NumSamples>12</NumSamples>

  </Configuration>

</UnitMonitor>