City Monitor – how to get started

ozgurCity CloudLeave a Comment

Earlier today we launched a new, free monitoring service in City Cloud. We simply call it City Monitor and yes, it’s free!

Here is all you need to know about getting started with those checks to make sure that you get notified whenever your web page or server is down and also to get a good view of your average load times.

 

Sign up for City Cloud

City Cloud is your one stop shop for cloud services in Europe. City Cloud is not just servers, it’s also storage, backup and monitoring and you can use any or all of the services as you wish. Step one is to sign up for City Cloud and log in.

If you already have an account

Well, proceed to login..

Create one or more contacts

Go to Monitoring in the top menu and then hit the Contacts tab and create one or more contacts. These contacts can be chosen to receive the reports later on.

Create contact

 

 

 

 

 

 

Creating your first check

  1. Go to Schedules and hit Create new schedule
  2. Name your schedule
  3. Choose your target and interval
  4. Choose which contacts should receive notifications
  5. Save

Create check

 

 

 

 

 

 

 

Congratulations, you have successfully created your first check and can now create up to 4 more.

Advanced settings

The advanced settings for the checks allows you to customize your checks even further.

Peer and streak threshold

To start with, City Monitor has 3 peers that check your web service status and more will be added along the way. The peer threshold determines how many of the peers must consider the service to be down before alerting your contacts. Right now, you cant change the peer threshold but we thought we’d inform how stuff works anyways. With the default setting a web service will only be considered down if 2 of 3 peers report downtime.

To make things even more customizable, we added the streak threshold (this one can be changed) to make your reports as correct as possible. At the default setting, a web service will only be considered down if two subsequent checks report downtime.

Both the peer and the streak thresholds work together so a web service can be set to either:

  1. Report downtime as soon as anything seems wrongThat would be a peer threshold of 33% (when we allow it to be changed) and a streak threshold of 1 fail during the last check.
  2. Report downtime when it seems more likely that there is an actual problemThat could be a peer threshold of 66% and a streak threshold of 2 fails during the last 2 checks.

So, basically you can set your thresholds to whatever you like. However, we recommend to leave the tresholds at the default setting to get a fair report and to keep you from going nuts from all the emails you are likely to get.

Conditions

What response time is considered downtime for your web service? Well, it’s up to you to determine that. The default setting is set to consider your service down if it doesn’t respond within 60 seconds. But of course you can set it to whatever you want and also add a couple of more conditions to that.

http code

Control if City Monitor should consider your web service to be down if the response is anything other than:

  • 200 (OK)
  • 301 (Moved permanently)
  • 302 (Found)
  • 304 (Not modified)
  • 403 (Forbidden)
  • Other (Customize yourself)

Response

This is a small detail but could come in handy for some users. You can actually set City Monitor to look for a certain string on the page you are monitoring. Just choose Must contain text and enter the string that City Monitor should search for and you’re all set.

 

Well, that’s all there is to know about how to get started with City Monitor for now. Have a go and tell us what you think!