topic Re: Debugging custom 2.0 extension with sqlOracle datasource in Extensions

Debugging custom 2.0 extension with sqlOracle datasource

sivart_89 — Tue, 02 Jul 2024 12:00:53 GMT

I've created a custom db extension but am noticing the below for an endpoint. I can connect to the database through something like dbeaver and run the query fine (the same connection string and account used in the extension). When ran through the extension it seems to not work. Is there any debugging I can do here to help determine what is going on? All of my other queries are working, just not this one query connecting to this other database.

Side note, this works fine in the old extension running from the same ActiveGate. Even so, based off the message below the connection does seem valid, there just isn't metrics being collected. I've seen a different message if the connection is invalid and the datasource cannot connect to the database.

Connection exists but no metrics have been produced for endpoints

Re: Debugging custom 2.0 extension with sqlOracle datasource

Mike_L — Thu, 04 Jul 2024 15:52:54 GMT

Hi,

This tool is helpful when investigating connectivity issues:

https://github.com/Dynatrace/db-connection-check

Mike

Re: Debugging custom 2.0 extension with sqlOracle datasource

Julius_Loman — Thu, 04 Jul 2024 19:57:18 GMT

It may sound dirty, but unless you use SSL, sometimes it's worth doing a tcpdump/wireshare packet capture and see what's going on. I'm not aware of any user setting to set the extension to debug mode. With Wireshark I was able to see the error almost immediately. In my case it was short name instead of fqdn retrieved from the SCAN name outside of my DNS domain resolutions.

Re: Debugging custom 2.0 extension with sqlOracle datasource

sivart_89 — Thu, 18 Jul 2024 12:14:05 GMT

Thank you all for your input here. Got pulled away from this a bit but looking now I no longer see the issue. I will keep these things in mind for the future.