This article applies to DPA version 9.0 and above and Ignite version 8.0 and above.
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.
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.
Modify the currently registered instance. This assumes the I1 instance is already registered once. If not, register it now.
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.