Words and Phrases
Managing Problems With Error Reporting
During discovery, many errors may be uncovered, for example, connection failures, hardware problems, exceptions, time-outs, and so on. You can drill down from the Trigger CI that caused the problem to view the error message itself.
DFM differentiates between errors that can be ignored (for example, an unreachable host) and errors that must be dealt with (for example, credential problems or missing configuration or DLL files). Moreover, DFM reports errors once, even if the same error occurs on successive runs, and reports an error even if it occurs once only.
For details on severity levels, see Error Severity Levels.
Error Table in Database
All DFM errors are saved to the discovery_problems table in the Probe Manager database schema. (The error information is saved to the database—and is not handled in the Probe's memory—to guarantee delivery to the server.) The Probe holds the latest list of problems for each Trigger CI. After each run, the Probe checks for changes and reports them in the Discovery Progress pane. For details, see Discovery Progress Dialog Box.