August 2008
Copyright © 2008 Isode Limited, London, U.K
Events generated by the Isode products are divided into three:
The different Severity Levels used by the Isode Event System are described in the table below:
| Severity Level | Description | Example | Operator Intervention Required | Administrator Intervention Required |
|---|---|---|---|---|
| Critical | A serious error has occurred, leading to total loss of service. | License file expired. | Requires immediate intervention. | As for operator. |
| Fatal | A serious error has occurred, which is likely to cause partial loss of service. | Running out of disk space. | Requires immediate inspection. | As for operator. |
| Error | An error has occurred, which may cause partial loss of service. The sub-system will usually recover from this without intervention. | Association Rejected to a remote MTA. | May require inspection. | May be appropriate to investigate repeated errors, or unusual error patterns. |
| Warning | Something unexpected has happened but is not causing a loss of service. | Protocol violation by remote system. | May be useful for operator to observe. | Administrator should perform non-urgent investigation. |
| Authfail | An authentication or authorisation failure. | LDAP Client authentication to server fails. | Operator may need to investigate. | Administrator should perform investigation of unusual warnings. |
| AuthOK | A successful authentication or authorization. | LDAP Client authentication to server succeeds. | Not usually useful for operator. | May be useful additional information for administrator. |
| Notice | Informative logging, recording major stages of operational processing. | Called service: smtp-external. | May be useful in monitoring low volume systems. | As for operator. |
| Information | Informative Logging, providing more detail than notice level. | Record each routing option reviewed. | Not appropriate. | May be useful to provide additional logging detail. |
| Detail | Informative logging at a more detailed level. | Log each X.400 checkpoint. | Not appropriate. | May be useful to provide additional logging detail. |
| Success | Informative logging, at a level similar to Detail. | Complete content conversion calculation. | Not appropriate. | May be useful to provide additional logging detail. |
| PDU | A logging option to record specific types of PDU (Protocol Data Unit). | Record LDAP Add PDUs | Not appropriate. | For use by experienced administrator. |
| Debug | Records information about progress and parameters within the program. | ckadr.c:360 normalised address OK (96). | Not appropriate. | Generally only useful when investigating complex problems in consultation with Isode support. |