You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

\n \n \n \n \n \n \n \n \n \n \n \n \n
Related DocumentationVersion of up.time AffectedAffected Platforms
\nAllAll
\n \n

up.time can be configured to record application configuration changes in an audit log named audit.log that is found in the logs directory.

\n \n

There are many uses for the audit log. For example, use the audit log to track changes to your up.time environment for compliance with security or other local policies. You can also use the audit log to debug problems that may have been introduced by a specific configuration change; the audit.log enables you to determine who made the change and when it took effect.

\n \n

The following is an example of an audit log entry:

\n \n

\n2006-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] \n

\n \n

Enabling the Audit Log

\n

The audit log is disabled by default. To enable the audit log:

\n \n
    \n
  1. Open the uptime_install_folder\uptime.conf file in a text editor and add the following line: \n

    auditEnabled=yes

    \n
  2. \n
  3. Save the file and exit the text editor.
  4. \n
  5. Restart the Data Collector. \n \n

    On Linux or Solaris systems, enter the following commands at the command line:

    \n \n
    \n/etc/init.d/uptime_core stop
    \n/etc/init.d/uptime_core start
    \n
    \n \n

    On Windows platforms, enter the following commands at the command line:

    \n \n
    \nnet stop "up.time Data Collector"
    \nnet start "up.time Data Collector"
    \n
    \n
\n
  • No labels