...
Audit Logging
up.time can record changes to the application's configuration in an audit log. The details of the configuration changes are saved in the file audit.log, found in the /logs directory.
There are many uses for the audit log. For example, you can use the audit log track changes to your up.time environment for compliance with your security or local policies. You can also use the audit log to debug problems that may have been introduced into your up.time installation by a specific configuration change; the audit log enables you to determine who made the change and when it took effect.
The following is an example of an audit log entry:
| Code Block | ||
|---|---|---|
| ||
2010-02-23 12:28:20,082 - dchiang: ADDSYSTEM [cfgcheck=true, port=9998, number=1, use-ssl=false, systemType=1, hostname=10.1.1.241, displayName=MailMain, systemSystemGroup=1, serviceGroup=, description=, systemSubtype=1] |
Enabling the Audit Log
By default, the audit log is disabled. To enable it, edit the uptime.conf file, which is located at the root of the up.time installation directory:
/opt/uptime on Solaris /usr/local/uptime/on Red Hat and SLESLinux-
C:\Program Files\uptime software\uptimeon Windows
In the uptime.conf file, locate the “"auditEnabled= ” " entry and modify it to be “"auditEnabled=yes ”. If the entry does not exist, add the entry to the file.
...
" (or add it, if it does not exist).