Version 3.2 - Root Cause Reveal and Alert Enhancements

Version 3.2 - Root Cause Reveal and Alert Enhancements

As we've done for previous feature releases, we're bringing you a new blog series taking an in-depth look at the major new features in v3.2.

Today's blog looks at a neat new enhancement which, although not the ‘biggest bang’ feature, we think your users are going to love.

For those of you who would rather a succinct summary of all new features, look no further than our "What's new in v3.2?" blog. For those of you wanting a deeper dive, let's go...

Over here in the marketing team we thought this feature deserved a fancy name (we have to earn our keep somehow!) so we’re calling it ‘Root Cause Reveal’ but we don’t mind admitting that really it’s just a cool little UI enhancement.

In v3.2, whenever you see a Status icon in a Warning or Critical state, you’ll also see why that Object is in that state, with Squared Up automatically surfacing the most recent, most critical, Monitor-based Alert for you.

This means that, at a glance, you can now see why your Objects are Red and quickly understand whether you need to fix the issue immediately or whether it can wait, without any further digging around to understand the cause of the health state change.

You’ll also find that other visualisations which utilise the Status icon - for example, the Dynamic Table - now surface this information too.

Dynamic Table highlight most recent, most critical issue.

Even better, Squared Up also surfaces this root cause on your Visual Application Discovery & Analysis (VADA) maps , so you can immediately see the key underlying issue for any given server in an overall application topology context too.

As you can see in the screenshots below, this Alert detail is available in both the simple ‘View’ mode and the more detailed ‘Analyze’ visualization.

But we haven’t stopped there, we’ve added a few other nice tweaks around alerts too.

For example, if you look closely at the first screenshot provided, you’ll see that one of the Critical Objects (SQL04) isn’t telling you why it’s Red.

Errors with closed Monitor Alerts won't surface this information


Well, that’s because someone has closed the Monitor-based Alert (tut, tut!), which we all know you shouldn’t do, you should go and fix the issue and then the Object’s Health State will change back to healthy and the Alert will close automatically. Naughty users!

For more on Monitor vs Rule Alerts and the enhancements we’ve made in this area for v3.2, stay tuned for our next feature blog…

 

Seeing is believing. Put this feature to the test in your own environment by taking a free 30-day trial and seeing Squared Up in action for yourself.

 

Related Content

© Squared Up Ltd 2017

Squared Up is a registered trademark of Squared Up Ltd. All other trademarks are the property of their respective owners. Privacy policy | Terms and Conditions