Once the server is running, point your web browser to it to see the status and configuration of the cache(s) being monitored. For example, if the server is running on localhost on port 9889, use the following URL: http://localhost:9889/monitorImage Removed
The web-based GUI is available by pointing your browser at http://<server-host-name>:<server-port>/monitor. For a default installation on the local machine, this would be http://localhost:9889/monitorImage Removed
The GUI contains 4 tabs, described as follows:
The list of functions supported by the API can be accessed by pointing your browser at http://<server-host-name>:<server-port>/monitor/list. For a default installation on the local machine, this would be http://localhost:9889/monitor/listImage Removed
This list shows the functions available. In addition to the parameters shown, each function has a format parameter, which can either be xml or txt. The default format is txt.
For example, the getVersion function returns the software version of the monitor server. It can be called as follows:
or, to receive the results as XML:
To query the data collected by the monitor server from scripts that can then be used to pass the data to enterprise system management frameworks, commands such as curl or wget can be used.
For example, on a Linux system, to query the list of probes that a local server on the default port is currently aware of, and return the data in XML format, the following command could be used
$ curl http://localhost:9889/monitor/listProbes?format=xmlImage Removed