"Features" Posts

Scout Client 2.0 is on the Horizon

By Derek Bullet_white Posted in Features Bullet_white Comments 1 comment

We’ve been working on two major features that we’re sure will be a hit, and that we can’t wait to talk about:

1) Easier Plugin Creation—there’s a reason we love Ruby, and not just because it’s such a powerful language for talking to external system processes and manipulating strings (as pointed out by JEG2 in our RubyInside debut). Ruby makes writing powerful code down-right simple through a very natural language. And with our new plugin code helpers and syntax, you can write a plugin like this:

my_output = `run some wild script here`
remember(:last_time_output => my_output)
report(:data => my_output)
if my_output ~= /Error/
  alert("An Error Occurred", "Details: #{my_output}")

And that’s not all. We’ve built a clearer syntax for how you invoke Scout, and how you interact with options and how you can store your own settings and report your own data.

2) Automatic Client Provisioning—if you have any servers in the cloud, or just more than one server, you already know how easy it is to install Scout (one liner to install and another to setup), but it just got easier than that. You can now automatically provision clients using the scout client itself. I know, crazy-talk, but watch. On bootup, of our Amazon EC2 instance, we’ll just run:

scout clone [client-key] `hostname` >> /etc/crontab

And we’ve just setup a new client on scout, with all our pre-configured plugins, cloned from another client, and the name of our hostname, setup to run on our interval.

If you’re interested in helping us beta test the new 2.0 version of our client, you can install it from our beta-gems server:

sudo gem install scout --source http://beta-gems.scoutapp.com/

Let us know what you think. Be sure to check the README to find out more details on what’s new.


Plugin Code is now cached

By Derek Bullet_white Posted in Features Bullet_white Comments Comments

One of the things people like most about Scout: the plugin code your clients execute is downloaded via a plain-vanilla HTTP or HTTPS connection like this one. This means you can simply update the plugin code once, and any clients that run the plugin grabs the new code. You don’t have to manually install scripts on each monitored server.

But what happens if the web server hosting the plugin code isn’t available? What if you are running a plugin someone else developed and they change the plugin code?

We’ve got you covered. Scout now caches the plugin code when you add a plugin to a Scout Client. By default, Scout locks to the version of the code available when the plugin was installed. However, you can override this and have Scout automatically grab the latest version. You can also perform a one-time update.

We check for code updates every 5 minutes, so if you are debugging a new plugin you developed, click the “Update Code” button when you push out a change to instantly refresh the code.

Read on for screenshots.

Read More →


Now with plugins ratings and comments

By Derek Bullet_white Posted in Features

We’ve received great feedback on our existing Scout plugins, but we wanted a better way to organize it. Friday we called on our inner agileness and built plugin ratings and comments.

Ruby on Rails Request Monitoring Plugin ~ Scout

If you have a Scout account, you can rate and comment on plugins in our directory. If you don’t have a Scout account, it’s completely free to signup – no obligations, late night phone calls, etc.

We’ll use your feedback to tune our plugins. If you have an idea for a new plugin, just add it to this thread in our forums.


Older posts: 1 ... 8 9 10