Denodo Platform offers you Diagnosing and Monitoring features through the Diagnostic and Monitoring tool which allows you to inspect the state of a server in the past, by graphically browsing its logs and visualizing it as well in real time so you can detect mal-functions as they happen.
One feature that would also be interesting for you to use, would be the Denodo Monitor, which is a JMX client that records different log activity of one or more Denodo Servers, and would be key for you as it records resources like CPU usage.
To configure **Denodo Monitor**, find the steps in the documentation for Denodo 8.0 on [Denodo Monitor](https://community.denodo.com/docs/html/browse/latest/en/vdp/administration/monitoring_the_virtual_dataport_server/denodo_monitor/configuring_the_denodo_monitor).
After configuring it, open your Denodo Home Folder > tools > monitor > denodo-monitor > bin and click on denodomonitor_startup file so that you can start Denodo Monitor.
Once that is done, go back to the denodo-monitor folder > logs and from “resources” you can get information on the CPU usage.
Now with that information, as mentioned above, since Denodo Monitor is a JMX tool and these files are exposed through JMX, you can use other JMX clients to access the same information on these resources.
You can read more through Denodo’s documentation on[ Monitoring with a Java Management Extensions Agent](https://community.denodo.com/docs/html/browse/latest/en/vdp/administration/monitoring_the_virtual_dataport_server/monitoring_with_a_java_management_extensions_jmx_agent/monitoring_with_a_java_management_extensions_jmx_agent).
Hope this helps!