This is the blog for Scout, Enterprise-grade server monitoring without the bloat.
70+ plugins, realtime charts, alerts, and Chef/Puppet-friendly configuration.

Cloud Monitoring in one line of code

Posted in Features | Comments Comments

UPDATE – Cloud Image Monitoring has been replaced by Server Roles

The greatest roadblock to monitoring is monitoring itself – installing software, tweaking scripts, remembering how to reload scripts, etc makes it painful process. It’s even more of an issue when setting up monitoring for cloud deployments – running a large configuration script or installing a lot of software with a saved image makes your environment very fragile, especially when deploying new servers is a frequent task.

We’re debuting a new feature in Scout that makes monitoring your cloud servers a single crontab entry – no scripts to setup, edit, reload, or coordinate across multiple instances.

Why use Scout for cloud monitoring?

  • Flexibility. Monitoring solutions that are saved with backup images or configuration scripts are difficult to update and test. With Scout, the monitoring profile for servers can be changed at any time in our web interface and doesn’t require changes to the deployment process.
  • Works across cloud providers. From Amazon ec2 to the Rackspace Cloud, Scout makes it easy to get consistent data across providers.
  • Affordable. As low as $10/per-server, per-month (comparable to Amazon’s Cloudwatch, but with far more functionality).

Overview

Scout now allows you to report from multiple servers with the same server key. When a server with a different hostname reports, a new server is automatically created in Scout with the same plugins, triggers, and settings as the original server.

This allows you to create profiles of different server roles in Scout (like web server, db server, etc) in point-and-click fashion and have any servers that perform that role report using the same key. If the original server is updated, new instances will pick up the changes (like a new plugin or editing a trigger).

An Example

You have a web server running in the cloud. You sometimes boot up more web servers if traffic increases from a saved image.

Install the Scout agent on a web server and add a cron entry. Setup your plugins in Scout. Save the image.

The next time you create a server using that image, the server will automatically appear in Scout under its hostname.

Enabling Cloud Monitoring

For any server you plan on cloning, simply check the ‘Cloud Image’ checkbox on the server settings page.

When another server starts reporting to Scout with the same server key, Scout will automatically create a new server in the interface using all of the same settings as the original server.

Comments

blog comments powered by Disqus
comments powered by Disqus