Error Severity Levels

When an adapter finishes running against a trigger CI, it returns a status. If no error or warning is reported, the status is Success.

Severity levels are listed here from the narrowest to widest scope:

Fatal Errors

This level reports serious errors such as a problem with the infrastructure, missing DLL files, or exceptions:

• Failed generating the task (Probe is not found, variables are not found, and so on)

• It is not possible to run the script

• Processing of the results fails on the Server and the data is not written to the CMDB

Errors

This level reports problems that cause DFM not to retrieve data. Look through these errors as they usually require some action to be taken (for example, increase time-out, change a range, change a parameter, add another user credential, and so on).

• In cases where user intervention may help, an error is reported, either a credentials or network problem that may need further investigation. (These are not errors in discovery but in configuration.)

• Internal failure, usually because of unexpected behavior from the discovered machine or application, for example, missing configuration files, and so on

Warnings

When a run is successful but there may be non-serious problems that you should be aware of, DFM marks the severity as Warning. You should look at these CIs to see whether data is missing before beginning a more detailed debugging session. Warning can include messages about the lack of an installed agent on a remote host, or that invalid data caused an attribute to be calculated incorrectly.

• Missing connection agent (SNMP, WMI)

• Discovery succeeds, but not all available information is discovered