Home
  •  

Connections Refused Due To Server Overload

Microsoft.LS.2010.Monitoring.UnitMonitor.ThresholdPC.AccessEdge_PERF_NET_CONNECTIONS_REFUSED_TO_OVERLOAD (UnitMonitor)

Knowledge Base article:

Summary

The total number of the connections that were refused with Service Unavailable response because the server was overloaded.

Causes

This server is overloaded.

Resolutions

This might be a temporary condition. If the problem persists, please ensure that hardware and software requirements for this server meets the user usage characteristics.

Element properties:

TargetMicrosoft.LS.2010.Component.AccessEdge
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.LS.2010.Performance.Double.DeltaThresholdMonitor
RemotableTrue
AccessibilityPublic
Alert Message
The total number of the connections that were refused with Service Unavailable response because the server was overloaded.
Perf Object Name: LS:SIP - 00 - Networking
Perf Counter Name: SIP - 006 - Connections Refused Due To Server Overload
Perf Counter Value: {0}

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

Source Code:

<UnitMonitor ID="Microsoft.LS.2010.Monitoring.UnitMonitor.ThresholdPC.AccessEdge_PERF_NET_CONNECTIONS_REFUSED_TO_OVERLOAD" Accessibility="Public" Enabled="true" Target="Microsoft.LS.2010.Component.AccessEdge" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2010.Performance.Double.DeltaThresholdMonitor" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Alert_The_total_number_of_the_connections_that_were_refused_with_Service_Unavailable_response_because_the_server_was_overloaded.">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Value$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Microsoft.LS.2010.Monitoring.UnitMonitor.ThresholdPC.AccessEdge_PERF_NET_CONNECTIONS_REFUSED_TO_OVERLOAD_OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error"/>

    <OperationalState ID="Microsoft.LS.2010.Monitoring.UnitMonitor.ThresholdPC.AccessEdge_PERF_NET_CONNECTIONS_REFUSED_TO_OVERLOAD_UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success"/>

    <OperationalState ID="Microsoft.LS.2010.Monitoring.UnitMonitor.ThresholdPC.AccessEdge_PERF_NET_CONNECTIONS_REFUSED_TO_OVERLOAD_UnderThresholdOverThreshold" MonitorTypeStateID="UnderThresholdOverThreshold" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

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

    <CounterName>SIP - 006 - Connections Refused Due To Server Overload</CounterName>

    <ObjectName>LS:SIP - 00 - Networking</ObjectName>

    <InstanceName/>

    <AllInstances>true</AllInstances>

    <Frequency>900</Frequency>

    <WarningThreshold>1</WarningThreshold>

    <ErrorThreshold>3</ErrorThreshold>

    <NumSamples>3</NumSamples>

  </Configuration>

</UnitMonitor>