Hello Dynatrace community,
I need to collect business data from GCP BigQuery. I tried to integrate this into "Generic DB Query Plugin" of Dynatrace ActiveGate.
I download latest Simba driver file SimbaJDBCDriverforGoogleBigQuery42_18.104.22.1684.zip to get GoogleBigQueryJDBC42.jar and others java libraries and put them in the right directory D:\dynatrace\remotepluginmodule\plugin_deployment\custom.remote.python.dbquery\jars
I also modify lightly dbquery_extension.py and plugin.json to be able to configure a endpoint of that new defined type.
It didn't works yet but the stranger thing is that i didn't found any errors even in deep diving logs into C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\dynatrace-ag-dbquery
Does somebody have experiences to help on that particular topic of integrations of new jdbc drivers, pls ?
Thanks by advance for your help.
Integrating a new JDBC driver for Google BigQuery into Dynatrace's "Generic DB Query Plugin" can be challenging, and it's important to ensure that every step of the integration process is correct. Since you're not receiving specific error messages, let's go through the integration process step by step to see if we can identify the issue:
1. JDBC Driver and JAR Files:
- Ensure that you have the correct and compatible version of the Simba JDBC driver for Google BigQuery (GoogleBigQueryJDBC42.jar) for your Dynatrace version.
- Verify that you've placed the JAR files in the correct directory (`D:\dynatrace\remotepluginmodule\plugin_deployment\custom.remote.python.dbquery\jars`).
2. Database URL and Credentials:
- In your `dbquery_extension.py` file, double-check the configuration for the BigQuery database URL and the credentials used for authentication. Ensure that they are correctly set up.
3. Plugin Configuration (`plugin.json`):
- Make sure that you've updated the `plugin.json` file to define the endpoint for the new JDBC driver type accurately.
- Check that the JSON structure is correct, and all required fields are properly configured.
4. Testing the Connection:
- Try to test the JDBC connection separately outside of Dynatrace to ensure that the driver and credentials are functioning correctly. You can use a simple Java program or a JDBC client tool for this purpose.
5. Log Verbosity:
- Increase the log verbosity in Dynatrace's plugin configuration. This can sometimes provide more detailed error messages that can help pinpoint the issue.
6. Restart ActiveGate:
- After making any changes, ensure that you restart the Dynatrace ActiveGate to apply the updates.
7. Permissions and Firewalls:
- Confirm that there are no firewall rules or network restrictions preventing the ActiveGate from connecting to Google BigQuery.
- Check that the credentials you're using have the necessary permissions to access BigQuery.
8. Dynatrace Community and Support:
- Consider reaching out to the Dynatrace community or their support resources. Other Dynatrace users may have encountered similar issues and can provide guidance or solutions specific to Dynatrace's plugin framework.
9. Review Documentation:
- Carefully review the documentation provided by Dynatrace for plugin development and integration, as it may contain specific guidelines or best practices for integrating custom JDBC drivers.
- Implement thorough error handling and debugging in your plugin code to capture and log any potential errors during the execution of database queries. This can help you identify specific issues with the integration.
11. Testing in a Controlled Environment:
- Always test your changes in a controlled environment to avoid impacting your production setup.
By following these steps and paying close attention to the configuration details, you should be able to identify and resolve the issue with integrating the Google BigQuery JDBC driver into Dynatrace. If you encounter specific error messages or face further difficulties, please provide more details for more precise assistance.