Home
  •  

DADE Receiver error folder is empty

Microsoft.Amalga.UIS.2009.Monitoring.ReceiverErrorFolderCount.Monitor (UnitMonitor)

Generates an alert when a DADE Receiver service has 1 or more messages in its Error folder.

Knowledge Base article:

Summary

DADE Receiver error folder is not empty.

Causes

Rejected messages are moved to the service instance's error folder. Since this is generally unexpected, this monitor alerts when 1 or more files exist is this folder.

Resolutions

Evaluate the message data and correct the issue with the individual message(s) and/or the feed source.

Element properties:

TargetMicrosoft.Amalga.UIS.2009.DADEServiceNode_Receiver
Parent MonitorSystem.Health.AvailabilityState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Amalga.Library.FileCountMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
DADE Receiver error folder is not empty
Environment: {0}
Computer: {1}
Service: {2}

Folder Path: {3}
File Count: {4}
Please see the alert context for details.
RunAsMicrosoft.Amalga.Library.Monitoring.RunAsAccount

Source Code:

<UnitMonitor ID="Microsoft.Amalga.UIS.2009.Monitoring.ReceiverErrorFolderCount.Monitor" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Amalga2009Discovery!Microsoft.Amalga.UIS.2009.DADEServiceNode_Receiver" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" RunAs="AmalgaLib!Microsoft.Amalga.Library.Monitoring.RunAsAccount" TypeID="AmalgaLib!Microsoft.Amalga.Library.FileCountMonitorType" ConfirmDelivery="true">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="Microsoft.Amalga.UIS.2009.Monitoring.ReceiverErrorFolderCount.Monitor_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="AmalgaLib!Microsoft.Amalga.Library.AmalgaWindowsServiceNode"]/Environment$</AlertParameter1>

      <AlertParameter2>$Target/Property[Type="AmalgaLib!Microsoft.Amalga.Library.AmalgaWindowsServiceNode"]/PrincipalName$</AlertParameter2>

      <AlertParameter3>$Target/Property[Type="AmalgaLib!Microsoft.Amalga.Library.AmalgaWindowsServiceNode"]/ServiceInstanceName$</AlertParameter3>

      <AlertParameter4>$Data/Context/Property[@Name='FolderPath']$</AlertParameter4>

      <AlertParameter5>$Data/Context/Property[@Name='Count']$</AlertParameter5>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UIGeneratedOpStateId03a7c7b107b842e2944d6da3cc46ef49" MonitorTypeStateID="LTThreshold" HealthState="Success"/>

    <OperationalState ID="UIGeneratedOpStateId240cf2f1e6ec475aad8a684177806708" MonitorTypeStateID="GEThreshold" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>900</IntervalSeconds>

    <SyncTime/>

    <TimeoutSeconds>300</TimeoutSeconds>

    <FilePath>SOFTWARE\Microsoft\Amalga\2.0\DADEServer\Message.Receiver\$Target/Property[Type='AmalgaLib!Microsoft.Amalga.Library.AmalgaWindowsServiceNode']/ServiceInstanceName$\Message.Receiver.Folder.Path.Error</FilePath>

    <PathIsARegKey>true</PathIsARegKey>

    <ThresholdValue>1</ThresholdValue>

    <StateWhenFolderMissing>LT_THRESHOLD</StateWhenFolderMissing>

    <DebugEnabled>false</DebugEnabled>

    <SubFolder/>

    <DebugEventSource>Amalga2009DADEReceiverErrorFolderCount</DebugEventSource>

  </Configuration>

</UnitMonitor>