This monitor is meant to alert customers of a known issue with the DADE. See product knowledge for details on this monitor.
DADE Receiver Received\UTF8 folder is not empty
Accumulation of large number of unused temporary files may lead to performance issues for the service.
This monitor alerts due to a known issue with DADE Receiver service. The issue can cause performance issues as the disk fills up with large amounts of unused temporary files. The issues is scheduled to be fixed in a QFE for the DADE. Consult an Amalga representative for availability details.
The receiver service is supposed to clean up its intermediate UTF8 files when finished processing a message. If this alert is occurring, the problem still exists on the system, or the QFE has been applied but the old unused files have not yet been manually removed from the system.
Stop the service and remove all unused temporary files in the service's Received\UTF8 folder.
Acquire and apply QFE #979381 for this issue.
In the absence of a QFE, some customers have implemented their own schemes for cleaning up these folders, such as:
- stopping the receivers once per day, deleting the UTF8 files, then restarting the receivers
- modifying the filer script to delete the corresponding UTF8 file after each file is successfully processed
- using the Deleter service, although the receiver really should be stopped before cleanup to avoid deleting a file which may still be in use by the receiver
All of these methods will have some chance of introducing noise with this alert since the alert was meant to trigger early (low count of files in the folder). If the alert is noisy when a custom cleanup solution is being used, you will need to override the file count for your specific deployment needs, either per service or the entire monitor.
It is recommended that customers acquire and deploy the DADE Receiver QFE rather than implement a custom cleanup to address this known issue.
Target | Microsoft.Amalga.UIS.2009.DADEServiceNode_Receiver | ||
Parent Monitor | System.Health.PerformanceState | ||
Category | PerformanceHealth | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Amalga.Library.FileCountMonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Microsoft.Amalga.Library.Monitoring.RunAsAccount |
<UnitMonitor ID="Microsoft.Amalga.UIS.2009.Monitoring.ReceiverUTF8FileCount.Monitor" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Amalga2009Discovery!Microsoft.Amalga.UIS.2009.DADEServiceNode_Receiver" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" RunAs="AmalgaLib!Microsoft.Amalga.Library.Monitoring.RunAsAccount" TypeID="AmalgaLib!Microsoft.Amalga.Library.FileCountMonitorType" ConfirmDelivery="true">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.Amalga.UIS.2009.Monitoring.ReceiverUTF8FileCount.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='Count']$</AlertParameter4>
<AlertParameter5>$Data/Context/Property[@Name='FolderPath']$</AlertParameter5>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateIda2e8eec5025b4b5fa9b22a1106e1ad84" MonitorTypeStateID="LTThreshold" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateIddf737d85745142099f35e1caab0527be" MonitorTypeStateID="GEThreshold" HealthState="Error"/>
</OperationalStates>
<Configuration>
<IntervalSeconds>14400</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.Received</FilePath>
<PathIsARegKey>true</PathIsARegKey>
<ThresholdValue>10</ThresholdValue>
<StateWhenFolderMissing>LT_THRESHOLD</StateWhenFolderMissing>
<DebugEnabled>false</DebugEnabled>
<SubFolder>UTF8</SubFolder>
<DebugEventSource>Amalga2009DADEReceiverUTF8Count</DebugEventSource>
</Configuration>
</UnitMonitor>