Visit Github if you cannot see the code below.
We’re delighted to announce two great new features today:
The Wormly SSL Testing Tool
Our newly deployed SSL Tester runs 60+ tests against your secure web server – in real time – reporting crucial compatibility, security and performance factors:
You can quickly share this information with your team using the permalink generated by each test. You will find this tool listed in our free tools section, or access it directly from the footer of any page site-wide.
Once-Off Downtime Scheduling
We’ve implemented a small, but often requested feature allowing one-off periods of host downtime to be scheduled:
To configure these periods, select Scheduled Downtime from any Host Overview page.
You can also now schedule a once-off Do Not Disturb period for your alert contacts via a similar interface.
You might be familiar with this situation:
The firewall sitting in front of your server farm fails, taking your public web site, extranet, API server, mail server down with it.
You’re a proactive sysadmin, so you’ve setup Wormly monitoring for all of these servers with alerts configured to hit your cell phone at the first sign of trouble.
As a result, you’re getting streams of alerts all which are telling you the pretty much same thing: Fix that firewall! All of those beeping text messages might help wake you up when this (inevitably) happens at 4am, but for that purpose our phone call alerts are a much better bet.
We’re pleased to announce a new feature designed to prevent such a flood of alerts. You can now configure Host Dependencies to define what other hosts a given host depends on.
From a host’s overview page, click the Host Dependencies link to get started.
Otherwise, just remember one important tip: Ensure that the shortest downtime triggering alerts on a host is equal to or greater than the testing interval of all hosts it depends on.
We’re delighted to announce the immediate availability of some exciting new – and much requested – features. The highlights include:
HTTP POST requests.
This enables monitoring of all kinds of interactions including login pages, registration forms, web services & APIs among many others.
Custom request headers.
You can now override any HTTP request header sent by our monitoring system. For example, you might override the Host: header in order to monitor a content distribution network / proxy. Or you might like to set the Referer: header to monitor a search optimized landing page.
Extended content match.
Allows you to match wanted and unwanted content strings in HTTP response headers. For example, you might monitor the correct functioning of a Location: [...] redirect by verifying that the correct response headers were sent by your application.
In addition to our HTTP sensor enhancements, we’ve added support for encrypted SSL and TLS connections for monitoring SMTP and IMAP servers, and have also enabled encryption for generic TCP Request sensors.
This will enable you to monitor a whole range of secured TCP services that we were not previously able to establish a connection with.
All of these new features are visible when you add new sensors or modify existing sensors. Naturally no extra costs apply to these features.
We’ve also rolled out a number of usability and performance improvements, with particular focus on the monitoring sensor creation and management process. We hope you’ll find using these new features a breeze!
Naturally we’d love to hear your feedback on these features – and indeed all aspects of our service. Drop us a line via the support desk and let us know how we’re doing.
Keep your eye out for loads more new functionality in the new year!
It’s been in private beta for quite a while now, so we’re very pleased to announce the immediate availability of the Wormly Developer API. Or ‘WAPI’ for everyone who loves an acronym.
Head over to:
And check it out. Or just click the “Developer API” link that you will now find at the bottom of every page.
We’re still in the early stages of WAPI’s development, and consequently the API coverage of Wormly’s functionality is by no means complete. With your feedback and suggestions, though, we will be increasing API coverage as quickly as possible.
So drop us a line if we’re missing something crucial to you!
Primarily to assist those who on-charge the cost of notifications (SMS, phone calls, etc) to their customers, the alert log browser now includes the name and numeric ID of the host that triggered the alert.
These records can now be exported in .CSV format in addition to being viewed on screen.
The alert log browser can be found under Settings, Alert Recipients, View Alert History (toward the bottom of the page).
Due to (somewhat surprising) popular demand, we have implemented a system allowing customers to make pre-payments of any amount to their Wormly account.
The pre-payment is added to your account balance, and used to pay subsequent invoices automatically as they fall due.
Additionally, the process includes the creation of a print friendly invoice. This can be handy if your accounts department needs to see some paper before they hand over the cash, figuratively speaking.
The pre-payment invoice can then be settled via Visa, MasterCard or PayPal.
Despite the prevalence of NTP, many sysadmins do not keep their servers running on the correct time. This is unfortunate, as it can make troubleshooting via log files much more difficult.
To celebrate 2008 finishing up one second longer than most years, Wormly now reports if a servers’ clock is running slow or fast via the Health Monitoring tab. e.g.:
So if you notice your servers running with an inaccurate clock, it might pay to put something like the following into cron:
/usr/bin/rdate -s time-nw.nist.gov
Note that this feature is currently only available for Linux servers. We hope to make it available for Windows servers in future.
Feature Deployed @ 2000-01-02 00:30 GMT
Owing either to high traffic events or server administrators going on holiday without a contingency plan, our users are likely to see lots of downtime throughout the festive season.
To help out, we’ve brought back the plain old telephone system.
As of today, phone call alerts are available in both our server health and uptime monitoring systems. For example, you can configure phone alerts if free disk space falls below 5% for more than 30 minutes – or if CPU load stays at 100% for a bit too long.
Calls are charged at a flat rate of $0.40 per call.
Naturally you can also configure a phone call if your site goes down altogether. A useful escalation schedule might be: Email when the downtime first occurs, send an SMS after 10 minutes, and make the phone call after 30 minutes.
We reckon that a phone call is still the best way to wake up your normally over-caffeinated sysadmin at 4am when The Bad Stuff happens. That little SMS *bleep* noise from their phone doesn’t always do the trick. And knowing that it’s all automatic is even better.
You can learn more about phone call alerts on this page.
Feature Deployed @ 2008-12-01 09:00 GMT
We’re very pleased to announce the immediate availability of our server health monitoring alert system; a feature which has been at the top of our most-requested list for some time now.
A simple screenshot explains it nicely:
Naturally you can also read about the feature in more detail.
For existing users, simply click on your hosts’ Health Monitoring tab and follow the instructions to start using this new feature.
Feature Deployed @ 2008-11-14 09:00 GMT
A blog hosted by James Peterson, director of insights @ Wormly
On a semi-regular basis James will be trying to demonstrate that website infrastructure really is an exciting topic, and that your users really do care about the uptime & speed of your website.