How to monitor your Droplets in detail, and not just their bandwidth, disk or CPU.
One of the basic principles for systems management is monitoring. You need to monitor to be able to guarantee availability, reliability, and performance of your systems. Whether you are talking about physical or Cloud, you need to monitor your servers and platforms. This tutorial addresses the added value ECmanaged offers to the monitoring of your Digital Ocean droplets or any other Cloud server.
Using the powerful monitor feature of ECmanaged will give you a complete overview of the status of your Cloud servers and applications. In this tutorial, we will show you just how easy it is to set up the ECmanaged monitor for an Apache web server and which valuable information the monitors will provide you with. Because being informed will allow you to maximize performance.
How to setup a monitor for an Apache web service
After creating a configurable LAMP Cloud server on Digital Ocean you can easily setup a monitor for the Apache web service. It will take you under 2 minutes. First, you need to navigate to the “Monitor” tab of your Cloud server.
The capacity and performance monitors are active by default. Click on the “NEW MONITOR” link and a 3-step wizard will pop up.
Step 1 of 3: Name the monitor
First, the wizard will ask you to name the monitor. This is important as it will allow you and our “autosolver” feature to identify the monitor later. The autosolver can then run actions based on specific thresholds. We will get to that in the next step. In this example, we will use the “Check HTTP” external monitor. By clicking the arrow you will go to the next wizard screen.
Step 2 of 3: Set the monitoring criteria
Now you are ready to set the monitoring criteria. How frequently does the monitor need to check? How often should it try before modifying its state? And, what should be the threshold for a warning or for a situation to become critical? You can alter these criteria or keep them on the default numbers. Click on the arrow to go to the final screen of the wizard.
The real added value of ECmanaged lies in its ability to react when and how you want it to. ECmanaged allows you to setup different reactions and schedule them in conjunction with the state of your Droplet or Cloud server (i.e., Critical, Warning, or Recovery). You can include as many reactions as you deem necessary to solve an incident. You can also define your own code, use the ECmanaged dictionary for typical monitors or even setup a reboot for the worst-case scenario.
Step 3 of 3: Save the data.
The monitor is created instantaneously.
After you defined the reactions you want ECmanaged to carry out, you should save the data. ECmanaged will instantaneously create the new monitor on its backend servers. It will feature on your dashboard alongside the capacity and performance monitors.
Conclusion: powerful monitoring as easy as 1-2-3
With ECmanaged you are not only able to monitor the capacity and performance of your droplets. ECmanaged provides you with a full set of monitors that you can install automatically. You just need to follow a simple 3-step wizard.
Using the ECmanaged monitor you are informed about the following metrics:
♦ Internal Capacity: CPU usage, Memory usage, Disk usage, and Network usage.
♦ Internal Performance: CPU performance, Memory performance, Load average, Process running, and Disk IO (Transactions, Bytes, Times).
♦ External checks: DNS, FTP (AUTH), HTTP/S (CONTENT), IMAP, MYSQL, PGSQL, MSSQL, PING, POP, SMTP, SSH, and TCP.
♦ Agent checks: Number of process (by name or regex), Process memory usage (by name or regex), and Service state.
♦ Application monitor: Apache Performance metrics, and MySQL Performance metrics.