Focus on business critical root problems

First the business, … and that’s all

Every one knows about standard UI console focuses about just IT elements, full of red the most of the time. Such UIs are just useless.

If you look at what your work is : it’s to run the business. Nothing more : IT is just here for this only purpose!

That why Shinken will help you focus on your business and root problems. It will show you which one is impacted, and what IT element is down.

Everyone got strongly dependent ITn N tiers applications and large networks are a standard now. Shinken can help you to find THE root problem when you have a problem “somewhere”.

Find the “root problem”

Or got only “useful” notifications

For a network dependency problem it will find THE source problem (here the firewall is down).

Stop the alert storm during a network problem

It can help you to find a source problem for logical dependencies (here the database is down, it’s useless to warn about the failed webapp).

Stop the alert storm during an application problem

Focus on business

Which admin is happy to be awaken by a SMS about a falling qualification environment? None.

In Shinken you can define the criticity of your applications. With it, you can filter notifications and UIs to print only business impacting problems.

Here for example a switch is the root problem, and it impacts a production application. You will raise a SMS to wake up the admin.

Root problem impacting production

But here the same root problem only impact a qualification application, there is no need to awake our poor admin.

Root problem impacting qualification only

Root problem and business in the UIs

Some UIs are already compatible with all theses new informations. One of the famous one is Thruk. With it, you can can see only root problems. And for each of them, you can see its impacts.

Here is an example of showing only root problems on the Thruk web interface :

Root problems in Thruk