How to resell server monitoring services

by Mark on January 23, 2012

We’ve now made it really easy for companies that offer web hosting and server hosting services to be able to resell server monitoring services to their customers.

The first phase of our reseller program is aimed at users of popular hosting billing software platforms ‘HostBill‘ and ‘WHMCS‘.

So how does it work?

Step 1. You will need your own Sentinel Server Monitoring account. To get this just head on over to sentinelmonitoring.com and sign up on our free 1 month trial.

Step 2. Once you have had a look around and seen how easy Sentinel server monitoring is to use and all the things that it can monitor – you can upgrade your account off the trial and onto a full featured Sentinel server monitoring account.

Now – We realise that some of you will want to try out the reseller part of Sentinel without having to pay anything. That’s fair enough. Unfortunately, the reseller portion can only be activated when an account has been upgraded. So you will have to put in a valid credit card number and upgrade the account. But here’s the deal. If you email us BEFORE you upgrade your account we can put some credit on there for you so you can make sure that the reseller options work for totally risk free.

Step 3 - Install the appropriate module into WHMCS or HostBill.  (You will need to be logged into Sentinel to download these modules)

Step 4 – We’ve put together a bunch of videos that show you how to set up the Sentinel Server Monitoring module inside HostBill or WHMCS. Have a look at the HostBill videos here .. and the WHMCS videos here.

That’s it! – You’re pretty much all done now.
We recommend that you take a look over our Reseller help article, this details the base costs for the reseller program, as well as the specific help article for HostBill and the specific help article for WHMCS

{ 0 comments }

Sentinel server monitoring now has a really simple interface to allow you to set periods of scheduled downtime for any server that you monitor.

While your server is in a period of downtime we’ll continue to monitor it but we wont send alerts for any problems that we detect. Scheduled downtime does not count towards your server availability detailed in your weekly report.

Click through the gallery below to see the process for setting Scheduled Downtime with Sentinel.

{ 0 comments }

New Sentinel checking node based in France

by Tim on September 10, 2011

We have just added a new checking node into our ever growing global server monitoring network.

The new node is at: 176.58.90.240 and is based in Paris, France.

{ 0 comments }

Massive server monitoring API update

by Mark on August 11, 2011

UPDATE: Our API is now live. Check out the documentation here.

A little while ago we launched a very simple API for Sentinel which we called ‘version 1′. Check out this example here on how we used it create a basic integration with Zendesk.

Well, over the last 6 weeks or so, Tim has been working away on creating a fully fledged API (‘version 2′) that will allow third parties to do pretty much whatever they need to with Sentinel from within their own systems.

So far we have full support for adding and removing servers, adding and removing services (checks) as well as the ability to add and remove contacts on your account and much more to come.

Tim has also been documenting everything so, before we release our brand spanking new website (that’s still a few weeks away), we’ll get the API documentation out as a public facing page so that you can all get busy with it.

All going well we will be releasing the API in about a week.

{ 0 comments }

We have just added a new checking node into our ever growing server monitoring network.

The new node is at: 209.177.145.225 and is based in New York, United States.

{ 0 comments }

People ask us this all the time, and while we put our new website together, we thought it would be a good idea to breakdown all the things that Sentinel can keep tabs on for you. So grab a coffee & stay focused because it’s a big old list.

Read more

{ 8 comments }

We have just added a new checking node into our ever growing server monitoring network.

The new node is at: 202.174.176.229 and is based in Sydney, Australia. That will keep things nice and fast for our friends across the ditch.

{ 0 comments }

We have set up a new checking node in Amsterdam, Netherlands and should help make confirmation checks from Sentinel monitoring even more accurate of those of you in Europe.

We have an Australian node coming online soon, stay tuned.

{ 0 comments }

As you may know the number of IP addresses are coming to an end (well all on the Internet as “we know it”) and as such there is demand to push more and more services and devices onto the Internet using IPv6 IP addresses. IPv6 IP addressing is somewhat different and, as such, requires a bit of trickery to make some existing systems work with it – hence the hesitation in transitioning to the Internet via IPv6.

At Sentinel we want to make sure you can monitor your servers anywhere (IPv4 or IPv6) and keep the experience as simple as possible so we’ve integrated IPV6 monitoring directly into our dashboard and it works just like ‘normal’ (IPV4).

For the techo’s out there you might be interested to know that due to the adoption of IPv6 we have used a technique called “dual stack” to allow our monitoring nodes to be connected to the Internet via both IPV4 and IPv6.

A number of the providers we host our checking  nodes with don’t currently provide “native” IPv6 connectivity to us and as such we are very thankful for Hurricane Electric’s tunnelbroker service. That allows us to connect to the Internet via IPv6 using their sweet system. Keep up the good work there guys!

We are really excited about this milestone, a quick Google shows there are less than a handful of companies providing monitoring of servers and devices on the Internet via IPv6.

If you have any questions about how Sentinel works using IPv6 please let us know.

{ 0 comments }

A few years ago, Tim and I (along with a couple of other friends) started one of New Zealand’s most successful web hosting companies – iSERVE limited. iSERVE grew quickly and, as a result of that growth, one of the major headaches we faced  was that we rapidly out grew our accounting system.

We were using MYOB and, despite reassurances, it just didn’t scale and there was no easy way to interface with it. In fact, I believe that Tim and Brent actually ended up hacking it apart so that we could get it to perform what we needed it to. That allowed us to interface with it .. sort of .. but it still wouldn’t scale. Enterprise solutions were well out of our budget then and we were stuck having to do a lot of manual work to make things tick along. Read more

{ 0 comments }