![]() This configuration is specific for FreeBSD (12 in my case but should be fine in any modern version) There are plenty of examples in the file, but I will drop my own configurations here as well, including a metin server which is what you're probably interested. Simple isn't it?įinally we get to the substance - the monitoring rules. Here we set a port, user and password to connect. Set alert not on Īnd here we can configure the web interface. Next goes the e-mail address where we want to receive the alerts: If you don't have your own mail server, you can send the e-mail to sendmail on localhost. I will detail here the options we should concern ourselves about - you can leave the rest as default.įirst is the mail server which we are going to use to submit mail alerts I entered here my own cPanel mailserver, where we previously whitelisted our IP (Exim Configuration/Access Control). Nifty isn't it? Here's how an e-mail from monit looks:ĭescription: failed protocol test at - HTTP: Error receiving data - Operation timed outĪnd then let's get our configuration ready.Ĭp /usr/local/etc/monitrc.sample /usr/local/etc/monitrc ![]() Monit is a very configurable daemon that can check virtually anything on our system -bandwidth, running processes, disk usage.- or even run custom scripts that extend its capabilities, and send us an e-mail to alert when, for example, we are running out of space, or our game server crashes. So let's get into action and introduce you to Monit. Yeah, because as much as we like mocking the Ymir programmers, those who worked in the original version were not stupid at all, and the fact that they chose the rock solid FreeBSD -which was a relatively new system back then- is a good proof of that. So I wanted to write down my experience in getting this tool to work in the best server operating system there is. As well crafted as monit and mmonit are, the documentation is somewhat obscure, particularly when it comes to FreeBSD. You may think that there is already enough documentation out there about popular tools like this - but you're wrong. ![]() So today I am going to introduce you to a free monitoring tool -monit- and to its paid console addon, which for some reason the programmers decided to name mmonit, creating unnecessary confusion. There is a myriad of paid options featuring flashy animated dashboards out there, but they mostly belong to the cash cow realm of SaaS which I try to stay away of. There are some nifty command line monitoring tools (glances, htop, atop come to mind) but when you have several server machines it can get quite frantic and besides - those tools do not offer a lot of flexibility.Īs we progress in the path to become a skilled server administrator (understanding server as in the machine and the software installed on it rather than in the Metin2 sense), it becomes necessary to use a remote monitoring tool that gives us some visibility on our systems. ![]() If you have ever had an incident on your server - cores crashing, filesystem getting full, lag ingame, or ddos attacks- you know that it can turn into detective work to find what is wrong, especially when we don't have a degree in CS. ![]()
0 Comments
Leave a Reply. |