https://community.dynatrace.com/t5/Open-Q-A/Explain-the-relations-for-database-monitoring/m-p/240030#M31518 <P>I hoped for same at latest database extensions but unfortunately it seems still remained splitted. 1 &amp; 2 can be joined via PG instance connections, but 3 - db extensions produces completely different entity types (f.e. for oracle: sql:com_dynatrace_extension_sql-oracle_instance), not connected (actually) to agent monitored hosts, PGs or db services.</P> Fri, 15 Mar 2024 12:08:48 GMT rastislav_danis 2024-03-15T12:08:48Z https://community.dynatrace.com/t5/Open-Q-A/Explain-the-relations-for-database-monitoring/m-p/240014#M31517 <P>Hello,</P> <P>As an example mssql has 3 ways it is detected:</P> <P>1- When a service does a query, dynatrace creates a "Database service"</P> <P>2- (When running on the same host) the oneAgent detects a process running the database service</P> <P>3- An extension (2.0) uses an end-point in its configuration</P> <P>I notice that Dynatrace knows that 1 and 2 belong together, how does this work?</P> <P>And how do I add 3 to the same?</P> <P>KR Henk&nbsp;</P> <P>&nbsp;</P> Wed, 03 Apr 2024 11:11:30 GMT https://community.dynatrace.com/t5/Open-Q-A/Explain-the-relations-for-database-monitoring/m-p/240014#M31517 henk_stobbe 2024-04-03T11:11:30Z https://community.dynatrace.com/t5/Open-Q-A/Explain-the-relations-for-database-monitoring/m-p/240030#M31518 <P>I hoped for same at latest database extensions but unfortunately it seems still remained splitted. 1 &amp; 2 can be joined via PG instance connections, but 3 - db extensions produces completely different entity types (f.e. for oracle: sql:com_dynatrace_extension_sql-oracle_instance), not connected (actually) to agent monitored hosts, PGs or db services.</P> Fri, 15 Mar 2024 12:08:48 GMT https://community.dynatrace.com/t5/Open-Q-A/Explain-the-relations-for-database-monitoring/m-p/240030#M31518 rastislav_danis 2024-03-15T12:08:48Z