Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Database Performance Analyzer (DPA) > Split out DPA monitoring by database within an instance

Split out DPA monitoring by database within an instance

This article applies to DPA version 9.0 and above and Ignite version 8.0 and above.

Introduction

Many times when multiple databases have been combined into one instance, the DBA would like a view of performance by each individual database or at least a segragated view of performance into the 2-3 larger databases. To accomplish this, DPA has the ability to register an instance multiple times, but then filter out/in databases to be monitored. For example, you could register Instance I1 3 times. The first registration can be configured to collect performance information from only the PROD database. The second registration could be configured to collect data from the DYNAMIC database and finally the 3rd could collect data from all other databases except for PROD and DYNAMIC.

Note: DPA puts less than 1% overhead on each instance it monitors, but when an instance is registered multiple times as described above, the DPA monitoring will be done 3 times per instance. The overhead would be around 3 times more than simply registering an instance once.

To accomplish the scenario described above where the I1 instance is registered three times, complete the following tasks.

Configure Ignite to Allow Mutiple Registrations of the Same Instance

Modify a system property to allow Ignite to register an instance more than once. This is a one time configuration and it is suggested to set this parameter back to false after registering an instance multiple times. This will prevent accidental registration of the same instance more than once when it is not wanted.

  1. Open the system.properties file in a text editor. This file is located on the DPA server in C:\Program Files\SolarWinds\DPA\iwc\tomcat\ignite_config\idc.
  2. Add the following parameter:

    # Allow instance to be registered more than once. This is good if someone wants
    # to register one database at a time in the same instance
    com.confio.idc.wizard.allowDuplicateDatabaseRegistration=true
     
  3. Restart the Ignite PI Server service.

Register the Instance Multiple Times

Modify the currently registered instance. This assumes the I1 instance is already registered once. If not, register it now.

  1. Stop the DPA monitor for this instance.
  2. Modify the QUICKPOLL_WHERE_CLAUSE to limit the databases it monitors.
    1. On the DPA Home page, click Options > Administration tab > Advanced Options DB Instance Options tab.
    2. Select the instance.
    3. Select the Support Options checkbox.
    4. Find the QUICKPOLL_WHERE_CLAUSE option and set it to:

      and db_name(s.dbid) = 'PROD'
      or
      and db_name(s.dbid) in ('PROD', 'IKB', 'Insight')
        -- if multiple databases are needed
       
  3. Modify the name of the instance that is currently registered (so we can register it again later).
    1. Click Options > Support tab > Database Query Tool and connect to the repository (it connects to this by default).
    2. To find the database ID and the current name, run the following statement:

      select id, name from cond;
       
    3. Run the following statement to update the name:

      update cond set name='newName' where id=databaseID; -- fill in the new name based on the databases this monitor will work with
       
  4. Refresh the DPA alert cache so alerts function after changing the display name. Choose Options > Support tab > Refresh Alert Cache.
  5. Restart the DPA monitor for this instance. It should be listed on the DPA home page with the new name.

Now you can register the instance again and go through Steps 1-5 above to have it monitor a different subset of databases. When registering, make sure to choose “No” for creating the monitoring user, as it is already there. You could also create multiple users, one for each registration of the instance. This may make it easier for troubleshooting.

Last modified
19:43, 4 Oct 2015

Tags

Classifications

Public