serverMonitor

WARNING: Experimental

Short abstract

Easy monitor the state of linux and windows servers, as well as the tools running on them.

Directly from your browser, see the state of all your servers in one glance.

How to

1. Make the jar by running gradlew pack
2. Deploy the tool on each server
3. Copy conf/sample.json to conf/monitor.json
4. Edit the configuration to match your needs
5. Start the monitor with java -jar serverMonitor.jar

What can be monitored ?

• Local to the server
  • System CPU usage
  • System memory usage
  • Disk usage on all root partitions
  • If specific processes are currently running on the server or not
  • Available system updates (apt-get and apt based only)
• Network
  • Pingability of other servers (either echo based or connection to a specific port)
  • Handshake with other servers running this tool (custom HTTP handshake)
    • If the monitor is not running on another server
    • Clock issues between servers

GUI

There is a GUI to monitor all the machines visible through the handshake.

From the GUI it is possible to:

• See the state of all monitored machines at once
• See the details for each monitored machine (What is working, what is not working, ...)
• See and update the settings of any monitored machine ** Note: Changing the web server port requires a restart to take effect

REST Apis

Seeing current status

Doing a GET on /status will return the current status of all monitors

Seeing current configuration

Doing a GET on /config will return the current configuration

Updating current configuration

Doing a POST on /config, with the new settings as a payload will update settings live. The new settings will be kept in memory, by adding the parameter ?persist=true, the new settings will also be persisted to disk.

NOTE: The web server port is the only setting which can not be updated through this method at this time.

How can it report ?

• Through the GUI (open http://localhost:9191 by default)
• Printing messages to the console
• Printing messages to a log file
• Sending notifications to a MessageCard compatible API (like Microsoft Teams)

Dependencies

• Oshi is used for system monitoring
• Jackson for JSON parsing and writing
• Jersey+jetty for the handshake server
• RestEasy for the handshake client
• Logback+Slf4j for logging
• Echarts for the charts
• Echarts for the UI

Planned features

• Yum based system update monitor
• A way too fetch current status through REST
• A way to see current config through REST
• A way to update current config through REST
• A way to fetch the entire cluster status
• A GUI
• Package www folder more easily
• More consistent configuration for each monitor
• Debouncer for failed monitors
• "Recovered" type of notification
• Windows update monitor (if possible without being admin)
• Monitor for installed services ** Sonarqube monitor ** Jenkins monitor