Monitoring the embedded Tomcat web container

You can translate the document:

Introduction

The Denodo Monitor is a tool included in the Denodo Platform that logs information about the Denodo servers. The standard configuration includes monitoring options for:

  • Virtual DataPort
  • Scheduler

The Denodo Monitor can operate as a standalone tool to collect logs from a single Virtual DataPort server, or through the Solution Manager Monitor, which enables you to collect execution logs from a single server or across all servers in a cluster or environment.

The Denodo Platform includes an embedded Apache Tomcat that can be used to deploy web services defined in Virtual DataPort. Therefore, monitoring this embedded Tomcat is useful for obtaining performance information when necessary.

This article describes how to configure the Denodo Monitor to include the embedded Tomcat in the list of monitored servers for both the Standalone Monitor of a Denodo Platform server and the Solution Manager Monitor.

Standalone Monitor

To configure the Standalone Monitor, edit the ConfigurationParameters.properties file available in the DENODO_MONITOR_HOME/conf folder as follows:

  1. Include Tomcat in the list of remote monitors by adding a new server called “tomcat” in  the section “Denodo servers that will be monitored”.

The result will be something like this:

monitors.remote=vdp,tomcat

  1. Define a Server monitor to log data about the running threads and memory usage of the embedded Tomcat creating a new monitor called “tomcat”.

The result will be something like this under the section “Server Monitors

tomcat.monitors=threads,resources

  1. Define the connection parameters to connect the Denodo Monitor to the embedded Tomcat including the following configuration in the section “Connection Parameters to the Denodo servers”:

# ==========================================================

# Connection Parameters to the embedded Tomcat server

# ==========================================================

tomcat.jmx.host=localhost

tomcat.jmx.port=9098

This example monitors the Tomcat included in a local Denodo Platform installation using the default port 9098. If the server is running on a different port, it can be modified by changing the value of the tomcat.jmx.port property.

Solution Manager Monitor

To configure the Solution Manager Monitor for a single Tomcat instance, follow these steps:

Open the ConfigurationParametersGeneral.template file located in         <SM_HOME>/conf/solution-manager/denodo-monitor/ and update the monitors.remote property from:

monitors.remote=[[VDP_SERVERS_LIST]]

to:

monitors.remote=[[VDP_SERVERS_LIST]],tomcat

Then add the following properties:

tomcat.monitors=threads,resources

tomcat.jmx.host=<host>

tomcat.jmx.port=<web_container JMX, 9098 by default>

This configuration enables monitoring of the embedded Tomcat for a single server. To monitor multiple nodes, update the ConfigurationParametersGeneral.template file as follows:

monitors.remote=[[VDP_SERVERS_LIST]],tomcat1,tomcat2,...,tomcatn

tomcat1.monitors=threads,resources

tomcat1.jmx.host=<host>

tomcat1.jmx.port=<web_container JMX, 9098 by default>

tomcat2.monitors=threads,resources

tomcat2.jmx.host=<host>

tomcat2.jmx.port=<web_container JMX, 9098 by default>

.

.

.

tomcatn.monitors=threads,resources

tomcatn.jmx.host=<host>

tomcatn.jmx.port=<web_container JMX, 9098 by default>

This enables monitoring logs for multiple Tomcat instances in a cluster or environment. For this change to take effect, you must restart the running monitors.

You can find more information about how to configure the Denodo monitor in the Virtual DataPort Administration Guide section Denodo Monitor. For more information about the Solution Manager Monitor refer to the Monitoring section of the Solution Manager Administration Guide.

References

Denodo Monitor

Solution Manager Monitoring

Disclaimer

The information provided in the Denodo Knowledge Base is intended to assist our users in advanced uses of Denodo. Please note that the results from the application of processes and configurations detailed in these documents may vary depending on your specific environment. Use them at your own discretion.

For an official guide of supported features, please refer to the User Manuals. For questions on critical systems or complex environments we recommend you to contact your Denodo Customer Success Manager.
Recommendation

Recommended resources Recommendations generated by AI

Logging incoming web requests

Startup of embedded web container

Using DynaTrace Application Performance Management with Denodo

Monitoring Denodo with Amazon CloudWatch

Best Practices for using the Denodo Monitor in Production Environments

Questions

Ask a question

You must sign in to ask a question. If you do not have an account, you can register here