Troubleshooting

At some point you may wonder why Argus thinks something is down or up (perhaps you tested it manually and you disagree), or why argus is doing such-and-such instead of other-such.

The debugging page contains all sorts of information about the object in question, some of which may useful for a tech to troubleshoot issues (but beware, this is no place for a PHB).

The meaning of some of the information will be obvious from its name or from reading the configuration documentation, some won't be obvious (and the author has no intention of documenting debugging output). In particular, you may find such things as: time of the last test, time of the next test, the reason a test failed, and the values argus is using for every configurable parameter.

Access to this information is controlled by 'acl_about'. To minimize confusion of management and/or end-users, it is recommended that access only be given to technical staff capable of understanding this information.