# Units for application\_wait\_time, cpu\_time, elapsed\_time in logs provided by Oracle DB extensions

**URL:** <https://community.dynatrace.com/t/units-for-application-wait-time-cpu-time-elapsed-time-in-logs-provided-by-oracle-db-extensions/50715>\
**Category:** Extensions\
**Tags:** databases, oracle, extensions\
**Created:** [March 14, 2025, 6:04am UTC](https://community.dynatrace.com/t/units-for-application-wait-time-cpu-time-elapsed-time-in-logs-provided-by-oracle-db-extensions/50715 "2025-03-14T06:04:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhijitmorye](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@abhijitmorye](https://community.dynatrace.com/u/abhijitmorye)\
**Post date:** [March 14, 2025, 6:04am UTC](https://community.dynatrace.com/t/units-for-application-wait-time-cpu-time-elapsed-time-in-logs-provided-by-oracle-db-extensions/50715/1 "2025-03-14T06:04:30Z")

</div>

Hello Community,

I was working on creating a dashboard using data provided by Oracle DB monitoring extension and I have one doubt regarding the units of metrics provided in logs by extension. Oracle DB extension fetched the the logs from all oracle instance with metrics like, application\_wait\_time, cluster\_wait\_time, DB\_time, for each executed query on instance. Please find the below snapshot of the data fetched by extension.

As you can see in the snapshot, for first query, elapsed time is very high however rows fetched by the query are in thousands only. This is where I am getting confused as even though i consider it as microseconds value, it is giving me very high value which looks unreasonable.

Can you help me on this to understand what is the exact unit value of all these time metrics.

Thanks

 ![abhijitmorye_0-1741931707074.png](https://global.discourse-cdn.com/dynatrace/original/3X/e/7/e7f39f34b724338b59b61c79bf46ad7c7f06c9c9.png)

---

<div class="post-metadata">

**Author:** ![apanoobee](https://avatars.discourse-cdn.com/v4/letter/a/8e7dd6/32.png) [@apanoobee](https://community.dynatrace.com/u/apanoobee)\
**Post date:** [November 27, 2025, 8:25pm UTC](https://community.dynatrace.com/t/units-for-application-wait-time-cpu-time-elapsed-time-in-logs-provided-by-oracle-db-extensions/50715/2 "2025-11-27T20:25:08Z")

</div>

Hi - have you found out the answer to this as I’m having the same issue. If you also don’t mind, can you please let me know how you managed to add the timestamp column? I’ve been playing with DQL and I’m still unable to view the timestamp column 😞

---

<div class="post-metadata">

**Author:** ![sujit\_k\_singh](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sujit\_k\_singh](https://community.dynatrace.com/u/sujit_k_singh)\
**Post date:** [December 11, 2025, 1:22am UTC](https://community.dynatrace.com/t/units-for-application-wait-time-cpu-time-elapsed-time-in-logs-provided-by-oracle-db-extensions/50715/3 "2025-12-11T01:22:03Z")

</div>

Hello&nbsp;[@abhijitmorye](https://community.dynatrace.com/user/85102)

The numbers in your screenshot (like 38,821,442,369 for elapsed\_time) look huge, which makes sense if they’re in microseconds. All time-based metrics provided by the Oracle DB extension—such as elapsed\_time, cpu\_time, application\_wait\_time, cluster\_wait\_time, and DB\_time—are reported in microseconds. These values come directly from Oracle dynamic performance views like V$SQL and V$SQLSTATS.

This is consistent with Oracle documentation: (See the oracle documentation on this&nbsp;[V$SQL](https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/V-SQL.html)&nbsp;)

ELAPSED\_TIME in V$SQL = total elapsed time in microseconds  
CPU\_TIME = CPU time in microseconds  
Wait times (application, cluster, concurrency) also in microseconds.
