Applications Systems
SAM AppInsight for Active Directory components do not show as Down even if monitored domain controller is Down
When a domain controller goes down it is expected that the Active Directory components monitored by SAM on the server would also go down, but they are showing as Up,
First published date
Last published date
Overview
Product section
Cause
The AppInsight for Active Directory application includes numerous event log and performance counter monitors. Component monitors that are successful complete in a more timely fashion, while those that fail in error take longer to complete as there are multiple retries made for each failed component.
Monitored components remain in their previous state until:
- A retry eventually returns a successful result,
- The number of retries, as determined by the Retry Count, is reached and the status returned is Down, or
- The Polling Timeout for the application is reached.
Whichever result occurs first impacts value displayed for the application in the Orion Web Console.
The Polling Timeout value is defined for the entire application/template, so the more components within the monitored application, the longer the Polling Timeout and Polling Frequency values should be.
Resolution
- Edit the application monitor to change the Polling Timeout value in the AppInsight application monitor to decrease the time SAM waits before it stops polling for application/component status. (The default polling timeout is 1800 seconds).
- When performing planned maintenance on a domain controller, unmanage the AppInsight for Active Directory application on the node during that time.