The following article will walk you through setting up RabbitMQ monitoring. LogicMonitor is fully equipped to gather both node performance and queue statistics of the RabbitMQ server.  To get started, you will need to set the following properties on your RabbitMQ device or group in LogicMonitor:  rabbitmq.user=[your RabbitMQ username] rabbitmq.pass=[your RabbitMQ password] rabbitmq.port=15672 rabbitmq.apiurl=[your RabbitMQ … Continued

Kafka is comprehensively monitored by LogicMonitor using JMX. This means that you will need to set up JMX (similar to other Java applications). 1. Before stating Kafka, export the environment variable JMX_PORT to configure Kafka to start with JMX enabled on the specified port. For example, to enable JMX on port 9999, edit your Kafka … Continued

LogicMonitor offers Oracle MySQL monitoring, providing visibility and analytics into database performance. It automatically detects and monitors key metrics, including query throughput, connections, replication status, and resource utilization; and enables proactive management and alerting to maintain optimal performance and availability of MySQL environments. Oracle MySQL Version 8 is a major update that introduces significant enhancements in performance, … Continued

With LogicMonitor’s Oracle package, you can monitor a large number of Oracle operations including blocked session metrics, library cache performance, backup and recovery activities, and resource usage. Oracle databases are monitored using Groovy with JDBC connections, through a user account with read-only permissions to statistics tables. If multiple instances are present, LogicMonitor will auto-discover them … Continued

Redis monitoring simply requires that the Redis process be accessible from the collector. By default the collector will look for Redis processes on the default port of 6379, but you can define additional ports to by setting the property redis.ports, on a host or group level. If using authentication, define the property redis.pass on a host … Continued

LogicMonitor’s MongoDB monitoring package offers monitoring for databases, server health, and replication for clusters. The package uses the MongoDB Java Driver to monitor the servers directly. Compatibility As of December 2023, LogicMonitor’s MongoDB package is known to be compatible with versions 6.0 or later. Setup Requirements Add Resources Into Monitoring Add your MongoDB hosts into … Continued

LogicMonitor uses JMX for monitoring Java applications. For information about Tomcat monitoring, see here. Enabling JMX JMX is enabled by passing parameters to the Java JVM during startup. For full instructions on enabling JMX monitoring within your Java applications, see Monitoring and Management Using JMX. To enable JMX monitoring of a java process with user … Continued

LogicMonitor monitors Tomcat with two approaches: HTTP to check the server availability and responsiveness JMX to collect comprehensive internal server statistics Monitoring Tomcat via HTTP The datasource HTTP- and HTTPS- check the server availability and responsiveness by sending requests to ports 80 and 443. If your Tomcat doesn’t listen on the standard port, or you have … Continued

In order for ActiveDiscovery to detect if a web server is using Apache, and to be able to collect statistics, LogicMonitor must be able to pull the /server-status page, which is served by the mod_status module.  By default, Apache does not allow access to this page. If LogicMonitor is not discovering Apache instances automatically, it … Continued

To collect information about the number of requests, busy threads, etc from Nginx, LogicMonitor must be able to pull the status page. Ensure Nginx is compiled with the stub_status module, and that the Nginx configuration file is set to allow the collector to pull the server status page, by a section such as the following in the … Continued