article Enabling Audit Logging in up.time

Related Documentation Version of up.time Affected Affected Platforms
All All

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

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.

The following is an example of an audit log entry:

2006-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

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

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

    auditEnabled=yes

  2. Save the file and exit the text editor.
  3. Restart the Data Collector.

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

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

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

    net stop "up.time Data Collector"
    net start "up.time Data Collector"
    

Related Articles


up.time causing excessive ESX connection logging

RatingViews
article

When up.time connects to an ESX server to collect performance data it registers a unique connection to the hosts API. This can cause an increase in logging on the server as each poll (for example...

By: uptime Support | Date Created: 8-6-2010 | Last Modified: 8-10-2011 | Index: 467

  1766

Enabling the IBM WebSphere service monitor

RatingViews
article

Before up.time can monitor a WebSphere server, you need to deploy the WebSphere performance servlet.

By: uptime Support | Date Created: 10-2-2006 | Last Modified: 7-29-2011 | Index: 096

  13229

Enabling the BEA WebLogic service monitor

RatingViews
article

To monitor a WebLogic server with up.time, first deploy the weblogic.jar file on the monitoring station.

By: uptime Support | Date Created: 10-2-2006 | Last Modified: 7-28-2011 | Index: 095

  6016

Access the View Applications dashboard without logging in

RatingViews
article

The 'View Applications' tab of GlobalScan is available directly via a URL reference without requiring a login to up.time. This allows you to display critical Application status information to users...

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 311

  4153

Agentcmd Logging Info Interferes With Custom Monitor Output

RatingViews
article

In 7.2 the agentcmd has extra logging enabled you are able to remove some of these logs by adding switches to the agentcmd command but the first line is always there:2013-09-19 12:50:03,704 -...

By: uptime Support | Date Created: 9-19-2013 | Last Modified: 3-15-2014 | Index: 600

  1844

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement