We’ve covered how to use the Pingdom Transaction Monitor to keep an eye on logins and form submissions before here on the blog. Today we will take that a step further and look at how you can monitor logins and applications that require basic authentication. We’ll actually present you with two ways of doing this: one using the Transaction Monitor and one using a regular HTTP check.
Archive for the ‘Tutorials’ Category
Imagine this scenario: You have just received an alert that your site is down and you log in to your Pingdom account to figure out what’s up (or down, in most cases). There you can see that your site is still down, and you now need to figure out what’s gone wrong.
Fear not, because that’s where the Root Cause Analysis comes in. It offers a set of diagnostic tools, which can help you figure out what caused an outage. In this article, we show you where you can find the Root Cause Analysis, and how to use it.
To highlight some of the most common issues reported by you, our customer, we will also publish some of the additions here on the Royal Pingdom blog. This is the first such entry.
Since we launched the Pingdom Transaction Monitor, we’ve seen a great response from you, our customers. The new check type has been used in ways we wouldn’t even have imagined just a short while ago.
We have already published a detailed article covering how to use the Transaction Monitor, but we wanted to give you a few more examples. So here we present ideas of how you could use the Transaction Monitor to keep an eye on login functionality and form submissions on a website.
We announced the beta for the Pingdom Transaction Monitor recently, and we’ve been expanding it to include more users. There’s been plenty of helpful feedback, much of what’s already been put into the pipeline for the future. The Transaction Monitor is on a fast development cycle, where the input from beta users is critical, so we appreciate all the help.
In case you have not yet tried the Transaction Monitor (and you can still sign up to be a part of the beta) we wanted to give you an idea of how to use use it. We think it’s a very easy-to-use, versatile and powerful tool, which can help you monitor multi-step transactions spanning several pages, scripts, etc.
Last week we made it possible for you to get Pingdom alerts via Twitter, giving you one more way to know if your website is down.
Initially we sent you alerts from a dedicated “alert account”, @pingdomalert, but some people also wanted to be able to have these alerts sent via their own Twitter accounts instead of TO them, so now we have added that functionality as well (i.e. alerts from Pingdom as your own status updates).
Let’s have a look at the different ways people are using these alerts.
Pingdom was made to directly alert our users of any downtime that might occur on servers and websites. But in many cases it’s a good idea to configure your Pingdom checks to first wait for a while and only alert you if the downtime continues.
In this post we give some recommendations on how to configure your Pingdom alerts to avoid getting alerts for temporary issues that might go away automatically before you even have time to get to a computer.