While discovering a cassandra server, why do i see many cassandra servers discovered?
Reason: It is because, by default, 'Discover all nodes in the cluster' option is enabled. If you want to monitor only particular instance, disable that option and add the monitor.
New to ADSelfService Plus?
Related Articles
While discovering a mongoDB server, why do i see many mongoDB servers discovered?
Reason: It is because, by default, 'Discover all nodes in ReplicaSet / Sharding' option is enabled. If you want to monitor only particular instance, disable that option and add the monitor.
While discovering a Redis server, why do I see many Redis server instances?
Reason: It is because, by default, 'Discover all nodes in the cluster' option is enabled. If you want to monitor only particular instance, disable that option and add monitor.
How to enable the Prometheus in Cassandra
How to Enable Prometheus Mode in Apache Cassandra This article explains how to configure Apache Cassandra to expose metrics in Prometheus format using JMX Exporter. Once configured, Applications Manager can collect Cassandra metrics using Prometheus ...
Discovering Tomcat server fails and it displays "Manageengine Agent has to be deployed for collecting the data from Tomcat Server".
Reason: Tomcat 3.x and 4.x cannot be discovered if Manageengine Agents are not deployed in it. Solution: To discover Tomcat 3.x and 4.x, download Manageengine agents, Tomcat3Agent.zip and Tomcat4Agent.zip respectively, that are bundled with ...
While trying to add a cassandra monitor, why am i getting "Unable to connect to the host / port" error message?
Solution: Applications Manager connects to Apache Cassandra via JMX. The "Unable to connect" error typically indicates that the Cassandra JMX port (default: 7199) is unreachable from the Applications Manager server, is bound incorrectly, or requires ...