Today we have added further functionality to our Server Monitoring feature, enabling more flexibility on when and why you are alerted. Also we’ve added the ability for these tests to detect downtime. … Read More
We're Always Busy
With StatusCake you're getting more than a static piece of software, we're working on updates every day of every week.
At StatusCake we’ve got a great range of integrations for alerting, today we want to take you through some of the advantages of using OpsGenie which differs from some of our other integrations in that it has several extra layers of setup beyond what can be configured in the StatusCake app.
On Call Scheduling
With the StatusCake-OpsGenie integration it’s easy to set up your different teams or individual staff under their own on call schedules. These can be set up on daily, weekly or custom rotations, and this allows for advanced scheduling scenarios like after hours, weekdays and weekends, or even teams based in different geographical locations. There’s also a handy tool called “Schedule Previewer” which allows you to instantly get an overview of your set up in this regard.
Detailed Alert Tracking
For every alert sent from StatusCake through OpsGenie, you will be able to view detailed tracking information. Within the OpsGenie activity log you can see when the alert was created and sent, who was notified, the time at which the alert was picked up by the recipients, and any logged action that has been taken.
As well as notifying multiple users at the same time, StatusCake alerts through OpsGenie can have escalation policies applied to them. This means that if the first team or individual to receive the alert does not pick it up for a set time frame the notification can then be forwarded on to another team, you can set this up to alert different staff/teams in order until the problem is resolved.
With the OpsGenie app installed on a mobile device it’s possible for staff to take appropriate actions in response to alerts that they receive. A set of default actions such as closing the alert and adding a note are available from the app from the get-go, and custom actions can also be added to suit your teams needs.
Alert parsing and type-change
Another great function available through the StatusCake-OpsGenie integration is the ability to parse incoming alerts from StatusCake, this means not just that they can always go to the right person with the right information, but also that you can choose to convert the type of alert that’s sent. When a StatusCake alert hits your OpsGenie dashboard it can then be automatically converted to an alert in Email, SMS, Mobile Push or Phone Call format.
Getting Started with this integration
If you already use OpsGenie, or if you were considering giving it a try you can view the set up guide here – if you have any questions just get in touch with our friendly support team who will be happy to help!
At StatusCake a large part of what we do is reacting to current downtime with alerts and logging historical downtime within reports. Today we’d like to take a look at how users can get the most out of customizing these factors.
On our Business level plan all alerts and reports via email can be fully customized to better represent your brand and ensure that the right information needed for your team to address issues quickly and efficiently is always present.
In the image below you can get an idea of the extent to which this is possible, all of our emails the get sent out can be modified as you see fit:
You can modify your alerts for Virus, Uptime, SSL, Domain, Page Speed and Server type notifications in a range of different ways. Each template is managed individually and will apply to all notifications for the set type – you can also set test-specific changes up if there are tests that you’d rather not use the blanket default settings. For changes to all tests you should go to the User Details section for setup, and for changes on an individual test level it’s just a case of editing the test in question and working with the three fields shown below:
When editing the email’s in the User Details section you’ll be able to change colors, logos and even the base HTML/CSS of the email. We’ve included a range of tags which can be included in the code which will grab data which can make these emails more useful and tailored to your team.
|||TITLE||||Displays Test Name|
|||SITE||||Displays Website URL|
|||TYPE||||Displays Test Type (HTTP/PING/DNS etc)|
|||QUOTE||||TestID and alert number e.g ( 12345 – 1)|
|||REASON||||Display Cause of Downtime|
|||TIME||||Display total downtime length for test|
|||HTTPCODE||||Display the error Status Code|
|||TESTID||||Display the TestID on it’s own|
|||CHECKRATE||||Display how often the test is checked.|
|||HOST||||Display Hosting provider if present|
|||CONFIRMEDTOTAL||||Show Number of confirmations for downtime|
|||MESSAGE||||Display custom content set per test|
|||TAGS||||Include tags attributed to the test|
|||VALID_FROM||||Display the date from which the SSL certificate is valid (SSL only)|
|||VALID_UNTIL||||Display the date from which the SSL certificate is no longer valid (SSL only)|
So for example, you could populate the subject field of the alert email with these tags, something like “Your Site: ||TITLE|| Is Currently Down 533 ||REASON||”
Reports will work slightly differently in that they are showing a historic downtime record for one or more tests, we can fully edit these as well in terms of appearance, title, sender address and tags, and changes will apply both to automatically and manually generated reports.
We use a different set of tags here which can be seen in the table below, bear in mind that these are report specific and will not work for alert type notifications.
|||CU||||Display Total Uptime percentage for tests in report|
|||WD||||Display Number of Tests with downtime|
|||WOD||||Display Number of Tests with no downtime|
|||TABLE||||Display Table of Tests with downtime|
|||UPTABLE||||Display Table of Tests with no downtime|
If you’ve got questions on this or would like to know more, feel free to get in touch with our friendly support team who will gladly answer any questions you have!
With StatusCake you can use a variety of methods to test basic “transactions”, including forms that deal with login, data protection and others.
Form and Raw POST data – We can send form or raw POST data along with our normal test requests, in many cases when dealing with HTML forms we can submit this data to the form in order to test the associated function.
Basic Authentication login – For pages where there’s not a HTML form to submit to, and instead access is gained through basic authentication. You can see an example of a Basic Auth dialogue below:
Content/String Match – Once we’ve submitted to the form or gained access to the page, it’s important to then verify that the expected page and results are returned. To do this we can use our Content Match feature. This will run a string match for one or multiple strings on the resulting page.
Final URL – You can use the Final URL feature to confirm that the page you’ve reached at the end of the process contains the correct URL, great for catching erroneous errors.
First of all you should assess which tools you need to use, and where the testing should be targeted. If you are dealing with a HTML based login form you should submit Form POST data, and your target should be the URL of that form rather than the main page URL.
If it’s a basic authentication job then your URL target should be that of the main page, and you should use the basic auth fields on the test on our end to gain access:
For other types of HTML form, which could be for a wide range of uses, you just need to grab the field submission names from the source code, these can again be entered in the Form POST field in valid JSON format with your desired values. This way you can use the feature to test pretty much any type of entry form.
Validating the Results
Once your form or login dialogue is being actioned, it’s time to set up validation of the process, this can be done in two ways.
String Match – Using the String Match field on the test you can confirm the presence of one or more strings in the source of the resulting page after whichever process has been carried out. You can be alerted optionally if these strings are found/not found.
Final Location – With this you can verify that the final URL in the process is an expected URL, for example if you are expecting http://mysite.com/allgood.php , but the URL reached is http://mysite.com/notgreat.php – you will receive an alert for the test.
Thanks for reading and just let us know if you’ve got any questions on this via our support channel!
Today we’ve launched two new changes that will be beneficial to our users in the country of Denmark, you can read about what’s been added below:
New Copenhagen based monitoring servers
We’ve added several new monitoring servers to cover Denmark and these are based in the city of Copenhagen, all paid users will now be able to select this location when setting up a test – it’s as easy as selecting Europe -> Denmark/Copenhagen in the test’s settings.
We hope that users find the ability to test from this new location useful, and remember if there’s a location you need that we don’t have it’s always worth getting in touch via our live support to let us know!
New payment currency – Danish Krone
We know that pricing in US dollars isn’t great for everyone. First off with exchange rates in such flux nowadays, If the US dollar is strong it makes us more expensive.
Secondly by being tied to another currency it’s likely that you’re paying a slightly different amount each month, and third maybe your debit or credit card company charges you a fee for making USD transactions.
We’ve made life simpler on this front recently by bringing in a wave of new payment currencies – and today we’re glad to announce that we will be introducing Danish Krone to enable our customers in Denmark to pay in their local currency! You’ll be able to pay in Danish Krone for our subscriptions on all terms, as well as additional SMS credits from here on in.