Business Service Management (BAC/BSM/APM/NNM)
More than everything monitoring, BSM provides the means to determine how IT impacts the bottom line. Its purpose and main benefit is to ensure that IT Operations are able to reactively and proactively determine where they should be spending their time to best impact the business. This covers event management to solve immediate issues, resource allocation and through reporting performance based on the data of applications, infrastructure, networks and from third-party platforms. BSM includes powerful analytics that gives IT the means to prepare, predict and pinpoint by learning behavior and analyzing IT data forward and backwards in time using Big Data Analytics applied to IT Operations.

Part 4: Diagnostics 9.20 - Increased flexibility around alerting and thresholds

Introduction

 

This is the fourth in a series of posts on HP Diagnostics 9.20, which was released several weeks ago during HP Discover.  Each post will talk about a specific new and/or enhanced feature or capability of this release of Diagnostics and how it will benefit you. 

 

The first, second, and third posts talked about new features called “Java Thread State Analyzer” , “.pdf export”, and “Dashboard Creator”, respectively.  All of these new features discussed how to increase your productivity and efficiency on a day-to-day basis. 

 

This post will not discuss a new feature, but rather enhancements to existing capabilities within Diagnostics and that is around thresholding and alerting.  Like the Dashboard Creator, these enhancements provide not only greater efficiencies, but also increased flexibility when it comes to investigating applications-related issues. 

 

 

More flexibility – 2 levels of thresholding

 

Prior versions of HP Diagnostics allowed a single critical threshold.  This prohibited having one alert for early warning and another for critical state.  With this release of Diagnostics, you can now set two thresholds – Critical and Warning – allowing for greater flexibility from an alerting standpoint.  The following screenshot shows the UI from Diagnostics where you set these two thresholds:

two thresholds.png

 

 

 

Automation – eliminate manually invoking a script

 

Prior versions of Diagnostics did not offer script execution options when an alert was triggered.  This version of Diagnostics allows you to execute a custom script when an alert is triggered.  Scripts can be Groovy- (ending in .groovy extension), Windows- (.bat, .cmd, .js, .ps1, .vbs), or Shell-based (.csh, .ksh, .sh, bash, etc.) scripts as well as native executables (.exe + Linux executable files, regardless of extension).  The way to set this up in Diagnostics is via “Create Alert Rule” as shown here:

Invoking scripts.png

 

 

 

 

Two things to note.  First, Diagnostics offers three (3) predefined scripts that you can use.  Second, you can pass arguments to the script. (See “Chapter 5: Working with Alerts and Rules” in the HP Diagnostics Users Guide.)  For debugging purposes, output goes to the server’s log, stderr, and stdout file sin the log directory.

 

 

Comprehensive – more metrics that you can alert on

 

With this release of Diagnostics, there are more metrics on which you can define thresholds and set alerts.  Before HP Diagnostics 9.20, it used to be just average latency.  With Diagnostics 9.20, it now includes things like average and total CPU, application server throughput and timeouts, etc., as shown in the following screenshot:

more metrics to set thresholds on.png

 

 

 

 

Conclusion

 

As you can see, alert and threshold enhancements as well as the addition of being able to automatically invoke a script provide tremendous benefits for not only IT Ops people, but also application developers.  For example, with two threshold levels, application developers might learn about potential problems a lot sooner and thus have more time to deal with the issues before they get out of hand.  IT Ops workload is reduced because they no longer have to perform manual tasks of starting or even executing commonly reoccurring tasks. 

 

Stay tuned for the next blog post on Diagnostics 9.20.  This post will discuss a new feature called Web Client Monitoring, which is especially useful for companies leveraging mobile business services – those companies that need to make sure the mobile applications underlying those mobile business services are not only available, but performing as expected.

 

Sonja Hickey

Senior Product Marketing Manager, HP BSM and APM

Sonja.hickey@hp.com

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
Sonja is a Product Marketing Manager for the HP Software Operations Center portfolio of products. She has 19 years of product marketing, pro...
Featured


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.