Distributed Monitoring
Distributed Monitoring Distributed monitoring is a method of website monitoring when the checking is performed from several locations.

Distributed monitoring is a method of website monitoring when the checking is performed from several locations. The main purpose for this is to exclude errors of checking server (which is always possible) from the site statistic and provide more precise result. Usually it is realized through the network of independent servers which check the sites one-by-one or simultaneously. The advangtages of such checks are listed below:

Checks are happening from different locations, just like the real users do.

If a single check fails - others may prove or decline the failure. So, probability of false downtimes is really low.

It is possible to overview the access and download speed from different countries and cities.

Possibility to catch network-related or DNS problems: site might be visible from your computer, but are you sure it works for everyone?

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.Availability
more glossary
"

I use it for free an just for having mail of when my website is down, and it's work very well, so I want to thank you.

"
- RA
Why a low uptime may affect not only your revenue, but also your company's reputation?

While you may be spending more time and resources on developing your website, you need to be sure that the core of the website is still performing well. There is a strong correlation between uptime and visitor conversions. Are you still wondering why is website uptime so important? Then take a deeper dive into this...

While you may be spending more time and resources on developing your website, you need to be sure that the core of the website is still performing well. There is a strong correlation between uptime and visitor conversions. Moreover, nothing drives your visitors to your competitors faster than multiple extensive and ongoing downtime issues. Are you still wondering why is website uptime so important? Uptime is being considered a critical metric of the website well-being. It reflects the percentage of time your website happens to be available to the visitors. Let’s take a deeper dive into this.

Track your website uptime or you put your business at risk

Imagine, you’ve already done all hard work – built a dream team of talented individuals (designers, copywriters, developers etc.), who are shouldering their delegated roles perfectly. And together you all created more than just a website - a master of the Google search that reflects on your personal brand. This suggests you put specific keywords and phrases throughout your website and your brand’s online profiles – so that if people go looking for you on Google, they are likely to find your website.

And there is someone who wants to visit your website, but a current outage is stopping him from camping on the webpage. No matter who you are, a multinational corporation or news portal, if your website goes down for even several minutes, it can impact negatively on your reputation, revenue, productivity and appeal among your visitors. Apparently, downtime is bad for your bottom line, but it costs differently within industries. Business size is the most obvious factor, but it is not the only one. Most of the visitors have a short patience span for even minor website hassles, especially when it comes to making major purchases. Therefore, ensuring your website stays up is a key to your successful business.

Inaccessible website is your clients’ losses

It seems that, inaccessible website puts the visitors off from using it. If your website is designed, for example, for reading books online but inaccessible at the moment, all your customers, including your loyal ones, wouldn’t be able obtain the information they need from your website. This suggests, all your readers won’t be able to get to know you and vice versa you won’t be able to connect to them. Imagine that right now there is someone who wants to buy or read a book from your platform. Try as he may, he can’t reach your website, because it’s closed. And now, he’ll think twice before going back to the platform that evokes frustration and irritation in him. He will definitely find another platform where buying and reading are much easier. Having an online 24/7/365 presence means you are very likely to gain more customers, increase your credibility and spread your business.

Server is down?

Reliability is a key piece of a good web hosting. Reliable web hosting providers not only try to keep the websites always online, secure, and fast, but also ensure that they’re reachable. Consequently, if you’re an unreliable hosting company, you put businesses that use your service at risk. Every minute their websites are down they are paying for it in business success and positive image among customers. What could it mean to hosting providers? In the era of an increasingly connected world, information spreads faster than ever. And we all know the power of customer reviews. Negative feedbacks mean little unless they have a profound effect on a company's ability to do business as well as the ability to stay ahead of the competition. When the company, in particular web hosting company, lost the faith of their clientele, this lead either to huge outflow of service consumers or potentially damaging situation for a brand.

Another example of how company’s reputation could be burned worst by downtime is an online store. Research shows that 60% of shoppers are surfing the net and even more read product reviews before making a purchase. There are many reasons why people choose not to shop at an online store, but perhaps the most striking is when specific website is down. Obviously, it would be a real struggle to keep the visitors on the website in case of a sudden server downtime. Downtime should be considered something to be avoided at all costs, because visitors are not going to wait at your doorstep. They’ll certainly leave your portal and never come back, as how they can lend an air of credibility to your website if you can’t help yourself…

Warren Buffet once said: “It takes 20 years to build a reputation and five minutes to ruin it”.

Out of a search engine?

Downtime issues contribute negatively to your search engine rankings as well. This implies, when Google try to rate your website and find out that it’s down, your website in most cases will temporarily drop in the Google search result rankings. Generally speaking, short periods of website downtime won’t hurt your search rankings that much, but long, consistent ones - will blow your rankings to bits. Scary?

Proactive monitoring of your website is the best way to stay one step ahead of any website bottlenecks and outages. You may rest easily using HostTracker service. HostTracker'll let you know whenever the incident is escalated, as well as, you will be in advance of your website issues. Spot problems before they arise and protect your business from losses that they can create!

 

 

 

more blog
Thank you for feedback!
 
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Blog
Использование REST и SOAP API Host-Tracker (Русский)

API-сервис разработан для тех разработчиков, которые желают интегрировать в свои приложения функциональные возможности, предлагаемые в Host-Tracker. Это можно осуществить с помощью простых Http-запросов (REST API) или же при помощи более сложных запросов, основанных на протоколе SOAP (SOAP API). Детальная настройка заданий по REST API и SOAP API.

Доступность сайта в сети — важнейшее условие его посещения пользователем. Пользователь, заходя на страницы веб-сайта, выполняет некоторые действия, которые в конечном итоге превращаются в материальную выгоду для владельца сайта — делает покупки, пользуется платными сервисами и прочее. Если веб-ресурс не был доступен какой-то период времени, то это оборачивается потерей репутации, прибылей, посетителей. Поэтому стабильность работы сайта следует отслеживать, мониторить его доступность в сети. Компания Host-Tracker предложила для этого ряд удобных сервисов, которые можно настраивать также, используя API сервиса Host-Tracker.

Поддержка REST и SOAP API

Host-Tracker предлагает возможность использовать сервис мониторинга как веб-службу, что очень удобно при необходимости создания десктопных, мобильных приложений, при осуществлении мониторинга большого числа веб-сайтов. Например, управлять мониторингом сайтов, количество которых переваливает за 1000, весьма проблематично. API-сервис разработан для тех разработчиков, которые желают интегрировать в свои приложения функциональные возможности, предлагаемые в Host-Tracker. Это можно осуществить с помощью простых Http-запросов (REST API) или же при помощи более сложных запросов, основанных на протоколе SOAP (SOAP API).

Настройка заданий

Настройка заданий по REST API может производиться в разных форматах. Заголовок Http-запроса Content-Type может быть определен как: application/json, text/xml, application/x-www-form-urlencoded (данные в виде «имя-значение»). В случае с SOAP API используется вызов удаленных процедур, что определены в технической документации сервиса. Примером таких функций могут стать: CreateHttpGetTask, CreateHttpHeadTask и множество других.

В рамках REST API с помощью POST запросов можно создавать задания: http-проверки, ping-проверки, а также проверки портов. Запросы, использующие метод PUT, позволят редактировать ранее созданное задание. С помощью GET-метода можно получить данные, принятые для настройки заданий или о самих заданиях, а при помощи DELETE-запроса предоставляется возможность удаления ранее настроенного задания. Так, запрос с методом GET к ресурсу api/web/v1/tasks/intervals в качестве ответа вернет данные о доступных в сервисе интервалах, которые определены следующими числами: 1, 5, 15, 30, 60. Для того чтобы получить те же значения, но через SOAP API, разработчику достаточно воспользоваться вызовом удаленной функции GetTaskIntervals. Использование метода POST совместно с ресурсом api/web/v1/tasks/http позволит создать задание Http-проверки.

Пример авторизации по REST API

Приведем простой пример авторизации в сервисе Host-Tracker, использующий простой Http-запрос. Чтобы выполнить авторизацию, необходимо послать POST-запрос для ресурса api/web/v1/users/token. В зависимости от выбранного формата поле заголовка Content-Type должно содержать одно из трех выше указанных значений. Например, если формат запроса и ожидаемого ответа должен быть в xml виде, тогда в поле заголовка должно значиться text/xml. Значение логина записывается в элементе <login>, а значение пароля — в <password>. Оба эти элемента являются дочерними узлами корневого элемента <LoginData>.

Рис.1.(Изображение, представляющее POST запрос авторизации в формате XML)

Авторизация в формате json также очень проста. Для ее реализации нужно лишь изменить значение ключевого заголовка Content-Type, а в теле документа передавать данные в формате json.

Рис.2.(Изображение, демонстрирующее POST запрос в формате JSON)

Детальная настройка заданий по REST API и SOAP API.

more
Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook