Documentation forDatabase Performance Analyzer

DPAIM relationship detection

When you integrate, the SolarWinds Platform retrieves information from DPA and attempts to create relationships between DPA database instances and SolarWinds Platform nodes and applications.

Relating nodes

Database instances and nodes are related by matching IP addresses or host names.

For IP address matching, the IPAddress property of the node is compared to the IP or Host property of the database instance. The database instance name can also be included in the IPAddress property, such as 192.168.110.132/dbi_instance.

For host name matching, the SysName and DNS properties of the node are compared to the Host property of the database instance. The database instance name can also be included in these properties, such as lab/dbi_instance.

If there are multiple nodes with the same IP address or host name, nodes monitored by an agent are removed from the potential relationships list. If there are multiple nodes remaining, you are prompted to choose a node on the relationship management page.

Relating applications

After nodes are related to database instances, the SolarWinds Platform finds the supported SAM database applications associated with each node. Application matches are refined further with different matching techniques based on the type of application. AppInsight for SQL and multiple template-based applications are supported. AppInsight uses database instance name matching. Template-based applications match based on the database instance name and component settings.

AppInsight for SQL

If a database instance name in DPA matches exactly with a database instance name in AppInsight for SQL, that relationship is mapped.

If a database instance name in DPA matches with a database instance name preceded by the default names for SQL instances, that relationship is also mapped.

SQL Server Performance

Relating DPA database instances to database instances monitored by a SQL Server Performance application uses the same database instance name matching as AppInsight for SQL.

The different templates also use the following components to create matches:

  • SQL Server 2005 - 2008 Performance (SQL) - User Connections
  • SQL Server 2005 - 2008 Performance (WMI) - Buffer Manager: Buffer cache hit ratio
  • SQL Server 2012 Performance (SQL) - User Connections
  • SQL Server 2012 Performance (WMI) - Buffer Manager: Buffer cache hit ratio

If a component is not set, the default template setting is used.

Oracle

If the DestinationPointType or DestinationPointName component matches the DPA database instance SID or ServiceName property, a match is made.

Sybase, MySQL, and Db2

The ports are extracted from the connection strings and compared.