Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Log DPA user activity

Log DPA user activity

Table of contents

Overview

DPA does not have internal auditing of user logins. If you are interested in tracking that activity (for example, to see the deployment success of DPA or for other reasons), complete the following steps to turn on auditing in the backend application server.

Environment

This article applies to DPA versions 9.0 and later, and Ignite versions 8.0 and later.

Steps

  1. Navigate to the directory DPA_home/iwc/tomcat/conf where DPA_home is where DPA is installed.
  2. Open the server.xmlfile in a text editor.
  3. Near the end, locate a line similar to:

    <host name="localhost" appbase="webapps"/>
     
  4. Replace this with the following:

    <Host name="localhost" appbase="webapps">
      <Valve className="org.apache.catalina.valves.AccessLogValve"
             directory="logs" prefix="dpa_access_log" suffix=".log"
             pattern="%t %h %{userSession}s %S %r %q" />      
    </Host>

     

DPA user logins will now be logged to the dpa_access_log.log file in the DPA_home/iwc/tomcat/logs directory.

Last modified

Tags

Classifications

Public