Here is an idea. Not verified by practical application, but it has grounding in the Oracle documentation.
OCI monitoring services by Oracle (don't confuse with what Dynatrace monitoring is) supports following services: https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/Content/Monitoring/Concepts/mon...
Note that among them, there are
-
Autonomous DB, which can be hosted on various infrastructures, including Exadata.
-
Metrics for Exadata database service which can be hosted on dedicated infrastructure - reportedly these metrics are emitted to the OCI monitoring services (per earlier link)
And these should be possible to monitor with https://www.dynatrace.com/hub/detail/oracle-connector-hub-signals-ingest/?query=oracle&filter=all - if customer sets them up so they are
-
emitted to the Monitoring service and later
-
transferred to Connector Hub, so they can be accessed externally, i.e by our extension
If this flow is set up - we should be able to receive the metrics. That's what the documentation from Oracle says. We don't have practical experience in this regard to guide customers on how to use these Oracle monitoring services and how to follow the Oracle documentation. We didn't test verify what Oracle says in documentation. So - It's on the customer side to try and see if they can set their services up that way so e.g. Metrics for Exadata database service will be emitted to the Monitoring service and transferred to Connector Hub, so external consumers, like Dynatrace, would access them via the Connector hub.
Then, what the Oracle Connector Hub Signals Ingest https://www.dynatrace.com/hub/detail/oracle-connector-hub-signals-ingest/?query=oracle&filter=all really does - should be just enough: get metrics from Oracle to Dynatrace. But, again, it's on Oracle customer's side to emit the metrics from the services of interest and make them available in Connector Hub.
