Applies to:
Denodo 8.0
,
Denodo 7.0
,
Denodo 6.0
Last modified on: 27 May 2020
Tags:
Administration
JMX
Monitoring
Denodo provides real time monitoring of all data service components in an integrated fashion, including Denodo platform components themselves and participating data sources. By analyzing parameters such as query response times, memory usage and CPU usage, etc, Denodo administrators can proactively rectify any potential data flow bottlenecks and determine when servers are at capacity.
All monitoring information is deliverable via the Denodo Dashboard and via SNMP and JMX standards. Denodo can therefore interoperate with most leading Systems Management packages.
Monitoring information can be saved for further analysis of how performance evolves over time. For these analyses, Denodo exposes server-side parameters (e.g., number of connections, memory and CPU usage, number of threads, data source usage, cache), along with statistics on query performance (execution time, number of rows, queries by type of CRUD operation invoked, use of cache, running status, etc.) and status indicators for each underlying data source.
Administrators can combine intelligence gathered from all of these monitoring sources to analyze the optimum performance of the Denodo server(s) and the data sources being virtualized as well.
In the following sections the MBeans exposing this monitoring information are explained in detail.
java.lang:type=Memory: management interface for the memory system of the Java virtual machine.
com.denodo.vdb.management.mbeans:type=MemoryManagementInfo: total memory occupied by the server, and memory peaks.
java.lang:type=Threading: management interface for the thread system of the Java virtual machine.
java.lang:type=Runtime: management interface for the runtime system of the Java virtual machine.
java.lang:type=OperatingSystem: management interface for the operating system on which the Java virtual machine is running.
java.lang:type=ClassLoading: management interface for the class loading system of the Java virtual machine.
com.denodo.vdb.management.mbeans:type=VDBServerManagementInfo: number of active connections and requests, instance name and instance role (master/slave).
com.denodo.vdb.management.mbeans:type=Cache,databaseName=<dbname>,subtype=DatabaseCache: cache information of a virtual database.
com.denodo.vdb.management.mbeans:type=DataSourceManagementInfo, name=GlobalDataSourceManagementInfo: number of data sources and active requests.
For every type of data source there is an attribute with the number of data sources and the number of active requests to that type of source.
Each virtual database has also its own MBean for its own data sources:
com.denodo.vdb.management.mbeans:type=DataSourceManagementInfo, databasename=<VDP database name>,aux=LocalDataSourceManagementInfo
Besides, each data source has its own MBean:
com.denodo.vdb.management.mbeans:type=DataSourceManagementInfo, dataSourceType=<dstype>,dataSourceName=<dsname>
com.denodo.vdb.management.mbeans:type= RequestsManagementInfo,databaseName=<dbname>: provides information on DML statements requests (SELECT, INSERT, UPDATE, DELETE, etc).
General Auditing
Detailed Auditing
com.denodo.vdb.management.mbeans:type=Cache,databaseName=<dbname>,subtype=DatabaseCache: cache information of a virtual database.
This MBean provides the operation getActiveRefreshCacheProcesses( <maxActiveCacheProcesses:integer>) that returns information about the processes that are currently inserting data in the cache of views of this database.
com.denodo.vdb.management.mbeans:type=Cache,databaseName=<dbname>,subtype=ViewCache,viewName=<viewname>: cache information of a view: status, last access, last refresh, current TTL, etc.
Denodo server generates different types of JMX notifications whenever:
The com.denodo.vdb.management.mbeans:type=VDBServerManagementInfo MBean provides the following notifications:
All of these notifications provide this information:
com.denodo.vdb.management.mbeans.CatalogManagementInfo,databaseName=<dbname>: provides information about the Data Definition Language (DDL) statements processed by the Server.
On subscribing to this MBean, notifications are sent every time a DDL query is executed (e.g., a new view is created, a view definition is modified, the privileges of a user are changed, etc.), or a transaction starts/ends with information on the statement/transaction.
com.denodo.vdb.management.mbeans:type= RequestsManagementInfo,databaseName=<dbname>: provides information on DML statements requests (SELECT, INSERT, UPDATE, DELETE, etc).
On subscribing, notifications are sent with detailed query information. Every time a DML statement is run on the database, two notifications are sent: one, indicating the beginning of the request and the other indicating the end.
com.denodo.vdb.management.mbeans:type= TransactionsManagementInfo ,databaseName=<dbname>: provides information about the transactions executed in a database of the Server.
It is possible to subscribe to the events of the TransactionsManagementInfo MBean. In that case, every time a transaction starts or ends on the specified database, a notification is received.