Monitoring your servers' resources
Cloud 66 automatically monitors resource usage on all servers deployed via our service. We monitor utilisation of the following:
This allows you to check whether your servers are experiencing high load and to diagnose any issues more quickly. Server Metrics are automatically collected and require no configuration.
Where to find server metrics
To find metrics for any server:
- Log into your Cloud 66 Dashboard
- Open the application in question
- Click through to a specific server
- Click on the Metrics tab above the main panel
You can also see Server-Group-level aggregates. These are visible on the Server Group page under the Metrics tab.
I don’t see my metrics?
If your existing server displays no metrics, you should deploy the application and all the required components will be installed and configured. This is a one-off action for existing servers. New servers will have metrics enabled on them by default. You may have to wait for up to 20 mins for the first data points to be displayed.
Understanding data collection
Cloud 66 automatically installs and configures the monitoring service (based on the Telegraf OSS project) on all servers. The service collects utilization data at 1 minute intervals and stores them for 7 days.
Options for additional monitoring
Most cloud providers now offer built-in server resource monitoring via their online dashboard, which can be a useful addition to your monitoring. If you need more specific detail (such as code-level monitoring) or or more granular reporting, we recommend implementing one of the many excellent cloud reporting solutions (see below).
Cloud 66 supports any third-party resource monitoring solution that is compatible with servers running on the two most recent LTS versions of Ubuntu. We have listed some commonly used solutions below, but this list is not exhaustive.
Adding external monitoring services to your app
There are two main ways to add an external monitoring service to your application:
- Using a deploy hook
- Manually, via SSH
Deploy hooks are generally the best choice because they integrate the monitoring tool into your deployment pipeline and ensure it will be rolled out to every server in your application when you scale up, and that the latest version will be fetched whenever you redeploy.
If you use a deploy hook, you should consider using Cloud 66's custom environment variables feature to manage the configuration variables for the service. This will allow you to control configuration without having to commit sensitive config files to your repo.
Common monitoring solutions
There are several excellent monitoring platforms on the market. For example: