Service Weather: Blocking or Degrading?

Back to news

As we have seen  in many other blog articles, the IT service weather is a simple way to communicate to managers, users, support, customers, …

Simple to understand (sun, cloud or rain) and at the same time accurately reporting the availability rate, IT weather provides for each user service (each “business application”), a real time view of the health of the application as well as calculating its availability over a selected interval.

Sharing this information is a real benefit to support staff, freeing them up to deal with their day to day tasks, especially during incidents.

At the heart of this communication is the need to avoid the financial implications of missed SLAs. Consequently, each user service must be built accurately and precisely to deliver the right information at the right time.


Elements of a user service and links

A user service is a functional representation of a business service or process; consisting of a set of technical checks linked together in a dependency hierarchy.

In ServiceNav, building a user service is based on 3 key elements:

  • hosts (is my server turned on?)
  • unit services (is my database accessible?)
  • and finally, other user services (is my AD is available?)

These items must then be connected to make sense of the importance of each check, host and user service in the overarching user service. For this, there are two types of links: blocking or degrading. We must ask the question of each host, a service, a user service “what is the impact on the overall user service that we are constructing of each element?”.

If I build the payroll user service: Would the fact that my database is not accessible have the same impact as a hard drive running at 85% capacity? Would the fact that there are a few too many users connected to the application at the same time have the same impact as a Windows service (IIS for example) not running?

It is when these questions are asked and answered that the strength of user services is revealed!

Using degrading or blocking connections along with the construction of intermediate user services and complementary management rules to manage, for example, clusters, it is possible to represent almost any application from a business perspective based on key technical checks.

Want to know even more?

Our documentation is available here

And our team is at your service: contact us for a demo.

UK ServiceNav Product Development Manager; my priority is to be needful of the particular requirements of all ‘English-speaking’ markets where ServiceNav is sold. I have over 20 years experience of the IT monitoring field - covering a wide variety of products and technologies.

More recent posts from the Servicenav team


Monitoring Azure IaaS, Azure PaaS and On-Premise IT: Case Study

Corporate IT is increasingly heterogeneous with both internal (legacy) and external components hosted by third-party vendors (Cloud). Monitoring of these different elements is a must… Read more


ServiceNav 4.3 – Dashlink, Timeframe improvement, Azure PaaS objects Plugins

Summary Dashlink – a new way to collaborate with Dataviz dashboards Would you like to be able to share part of the management console with… Read more


Monitoring: A Suggested Roadmap for Choosing the Right Tool – Part 2

We saw in the previous article the issues and methodology surrounding selection of monitoring tools.  Now let’s see how to implement this using a real… Read more