Want to monitor your VPS or dedicated server? Check out our management and monitoring options here!
How it works
We use the CheckMK software suite to provide monitoring capabilities.
In order for monitoring to work, a monitoring agent package must be installed and configured by our support staff on your Linux OS.
You will then be able to log into https://monitoring.flokinet.is (with a new username and password) and see a complete live status report for your servers.
Please note: if you reinstall your OS, the monitoring agent must be installed and configured again. You can contact support via ticket to perform this operation.
What are the monitored metrics?
These are some of the system features you can expect to see with the monitoring service:
- Basic system status: CPU, RAM, network usage, I/O, etc.
- Updates: Status of APT updates
- System services: systemd, NTP, etc.
- SSL/TLS certificate validity on port 443.
- Servers: NGINX and Apache server status
- Docker daemon status
- Hardware status: Temperature, S.M.A.R.T. parameters, software RAID, etc.
- Filesystems: status and usage of local and network filesystem mount
- many more
Technical setup details
Firewall access
For monitoring to work, the host at monitoring.flokinet.is must be able to connect to your server on TCP port 6556. If you are using any kind of firewall, make sure to keep port 6556 open.
Webserver configuration
In order to monitor NGINX, the stub_status module must be installed and availableroot@linux:~# nginx -V 2>&1 | grep -o with-http_stub_status_module
with-http_stub_status_module
For Apache, the status module should be enabled.
MySQL configuration
For MySQL to be monitored, FlokiNET must create a "monitoring" user in the database, with complete read rights over the whole database engine. Do not remove this user as monitoring will use it to query database information.
