Hello.
Indeed Exadata exposes metrics via prometheus and the extension scrapes them. These are the infrastructure-level metrics. After all, Exadata is an infrastructure layer and metrics for Exadata as the infrastructure-layer metrics. Rich, complex and Exadata-specific, but still it’s the infrastructure layer
Oracle database runs on this infrastructure - so one layer above - and Oracle database monitoring would expose the database engine/structure/query execution-level metrics. This logical layer is monitored by the Oracle database extension.
App server is one more layer above - query executions reported by OneAgent on app server are executed against the database seen by the app server. In order for Davis AI to walk this topology, it has to have ways of connecting layer-to-layer dependencies on specific entity level. Of we speak about query-level diagnostics, unique query identifier would have to be known all across the path.
The former - horizontal and vertical entity-level dependencies - is what the Smartscape has been designed for. The latter - query execution tracing across the supporting apps, systems, infrastructure - is only possible where some trace IDs exist. Oracle does not yet provide tracing of queries across its databases and underlying Exadata infrastructure. Maybe some day. It’s a question to Oracle. Dynatrace is ready to import and analyze OpenTelemetry signals from any source.
Going back to the former - horizontal and vertical entity-level dependencies - short answer is that in the Smartscape classic there are limited ways of tracing such topology end to end. So - these will be separate data sets, indeed. That’s the reason why we are moving to the Smartscape on Grail - it opens the ways to stitch topological representations of distinct technologies through deterministic connections between their edges. We have just started this route, all extensions are getting Smartscape on Grali support now; Exadata extension with Smartscape on Grail support will be available in upcoming few weeks as well.
Please note though that it doesn’t automatically mean the entire topology will be stitched together across all monitored technologies and ecosystems. Smartscape on Grail opens this possibility, but there is still work to do on both our, partners, integrators and customers side to use these possibilities in practice. But the topologies will exist on the same level - available via the DQL Smartscape queries - ready to stitch them, so Davis will be able to walk across them.
Featured Posts
