We’re pleased to announce the immediate availability of injecting Wormly Alerts into Discord chat rooms and Microsoft Teams Chat:
Read our guides explaining how to integrate Discord and Microsoft Teams. Oh and we’ve also supported Slack for quite a while now!
We’re pleased to announce the immediate availability of HTTP/S monitoring of web servers over the IPv6 network.
By default all tests are conducted over IPv4. To enable IPv6 you need to set the IP Mode to IPv6 only in your sensor configuration as shown below:
This will cause the IPv6 address to be resolved from the hosts’ AAAA record. If required, you can override this IPv6 address by entering the desired address into the Force IP Address parameter field.
We’re also pleased to announce an addition to our suite of free test tools; a realtime HTTP tester.
Under the hood, this uses the same HTTP client implementation as the rest of the Wormly monitoring network, so it’s a useful way to perform manual tests when choosing your automated monitoring strategy within the Wormly dashboard.
You can also share the results of each test conducted simply by sharing the URL generated, a great way to work with your team resolve issues together. Naturally you can use it to perform IPv6 tests, too!
If you have multiple web servers sitting behind a load balancer or within a Content Distribution Networks (CDN), you can now monitor them individually so long as they are reachable via a public IP address.
The Wormly HTTP sensor parameter Force IP Address allows you to target a specific web server using SNI. Simply enter the IP address of the web server you wish to target in that field:
This new feature is handy for monitoring a specific server in a CDN – or a single server within your load balancing cluster. Naturally it also works with regular HTTP requests.
We’ve just deployed an incremental improvement to the web & mobile UI: Test response inspection now includes code highlighting for HTTP, JSON, JS, HTML/XML:
At ~01:00 UTC on Sunday May 20th the database cluster which underpins the Wormly Metrics service suffered a partial outage.
This caused the failed receipt of Metrics for all customers, as well as a secondary effect which in some cases included incorrect alerts being sent. If you experienced spurious alert messages during this time please let us know and we will ensure these are refunded from your account.
The duration of the outage was, unfortunately, lengthy. Service was restored at 04:20, with some short periods of instability over the following 3 hours.
The Uptime Monitoring service was not affected by this outage.
Currently our post-mortem is underway so we don’t yet have a firm idea of the cause and what the possible mitigations might be for the future. We will keep you updated.
We’re in the uptime business, and really regret any downtime whatsoever. So on behalf of Wormly I apologise for this incident and promise that we will continue to do our best to keep improving. The availability of the Metrics service has exceeded 99.9% in the past 24 months, but I’m sure we can do better.
Regrettably we woke up some of our beloved sysadmin users last night – those whom reside in the Asia/Pacific time zones at least. A number of false alarms were issued by Wormly – owing to a recent update to our asynchronous DNS resolution intended to improve the performance of our Uptime Monitoring system.
As it turns out there are still some issues with this library when operating under load, and this resulted in 3 instances of spurious “Timeout while contacting DNS servers” errors between Tue, 23 Jul 2013 21:15:21 +0000 and Wed, 24 Jul 2013 21:05:00 +0000. The deploy was reverted at this time.
A total of 528 erroneous SMS & Phone Call alerts were sent as a result. These have been removed from the affected accounts to ensure that users are not charged for these messages.
We’re acutely aware that false alarms – especially those that unnecessarily wake you up – are an enormous failure on our part, and for this we are deeply sorry. We have already increased the sensitivity of our internal monitoring of these processes so that we could catch anomalies like these faster. We are also working to improve our integration testing environment to add tests which might reveal these kinds of problems pre-deploy.
Please do contact support if you have any other concerns surrounding this incident – we want to make things right for you.
Once again, we’re really sorry to have failed you – and we’re working hard to minimize the risk of breakages like these and others in future.
TL;DR:
Hit the “/” key and start typing part of a host name, URL, email, phone number then hit “ENTER”. Or “TAB, g” to see graphs.
You might not know it, but Wormly has many keyboard shortcuts available: (Hit ? to see them on any page within the app)
Those of you who prefer to avoid the mouse or trackpad have probably already discovered these. Today, however, we’ve shipped a major update to the keyboard UI, notably around the search facility.
Previously you could hit “j, j” to bring up a simple jump-to-host list. Whilst that shortcut still works, we’ve switched to “/” as the trigger because the forward slash has become the standard way to invoke site-searches around the web.
And our search facility now also searches your Sensors and Alert Contacts:
We’ve also added some extra hotkeys which allow you to jump directly to a hosts’ Graphs and Uptime Reports. When you’ve selected the host of interest – either with an exact search term or the arrow keys – you can hit TAB, g to jump straight to that hosts’ Graphs, or TAB, u, for its Uptime Reports:
Note that all of these hotkeys and behaviours are also found in the search box on the My Hosts page. No need to hit slash there; since the search box has focus on load. Happy searching, power users!
We’ve just shipped a feature much requested by many of our larger customers; every change made to your monitoring configuration is now logged.
In addition to a brief explanation of the event, the timestamp and responsible user is logged.
Users can also add notes to each activity explaining why the change was made.
You’ll find Activity Log linked from My Account.
[Also see our FAQ entry on SSL Certificate Monitoring here.]
An outage caused by an expired SSL certificate is the last thing your DevOps team want their inboxes filled with.
Although, happily, the odds are pretty good that they’ll already be awake when it happens, given that certificates are generally issued with an expiration time identical to the moment the certificate was signed. We presume they weren’t purchasing SSL Certs in their sleep.
Still – much better to ensure that the right people are alerted before expiration. And now Wormly can help you with this small, but critical, task.
You will find a new parameter available in our HTTP Sensor – simply specify the minimum number of days validity that a certificate must possess. Alerts will be generated if that threshold is exceeded.
Note that all certificates presented by your server (i.e. the complete certificate chain) will have their expiration dates checked. So a soon-to-expire intermediary certificate won’t go unnoticed, either.
Today we announce Clarity, our new test platform. Clarity offers drastically lower test intervals, right down to 5 seconds – a level that none of our competitors can match.
With Clarity, you can be confident that even the most isolated of failures will be detected and reported. Mission critical systems can now get the level of attention they deserve.
Clarity represents a significant evolution of our core test product, and further improves the already impressive fault tolerance of our distributed monitoring system.
The improved performance of Clarity has allowed us to double the test frequency for all customers on our current plans to 30 seconds, at no extra cost.
Gold, Platinum and Enterprise plans now include High Definition monitoring sensors, at no extra cost.
As always, you can view full pricing details from within your account, or choose from our other plans to find one that suits your needs.
