01 Oct 2024
10:48 AM
- last edited on
07 Oct 2024
09:45 AM
by
Michal_Gebacki
Hello,
From the extension documentation I read: As of now, only WMI extensions and Prometheus extensions can be run locally.
And from "The Oracle Database Monitoring Configuration"
https://docs.dynatrace.com/docs/extend-dynatrace/extensions20/data-sources/sql/oracle-monitoring
I read: "you need to identify the databases you'd like to collect data from and identify the ActiveGates that will execute the extension"
So this means that the "SQL data source" can only be activated on an ActiveGate.
Does this have any practical reason or is this an implementation limitation?
KR Henk
Solved! Go to Solution.
05 Oct 2024 07:06 PM
Hello @henk_stobbe
Thanks for raising these points, we have already exposed such scenario where :
Oracle DB monitoring requires configuring one agent features :
Mainly the communications between the AGs and the Oracle DB instances should be conducted properly on port 1521.
You can either configure it through:
You're right regarding WMI extensions and Prometheus extensions can be run locally.
KR,
Peter.
10 Apr 2025 01:37 PM
Hi Peter,
would I be able to use the local OneAgent on the DB server, using an instant client with an Oracle wallet?
The advantage would be, that Dynatrace don't need to have the password for the DynaTrace Oracle user and that the DB responsible can change the PW in DB & Wallet without updating the credentials in Dynatrace
Rgds
Bernhard