• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates
  • Administration

This community can have members from outside your organization. WebSphere Peformance - Alexandre Polozoff's Point of View

  • Log in to participate

▼ Tags

▼ Archive

  • December 2016
  • November 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • February 2015
  • January 2015
  • October 2014
  • August 2014
  • July 2014
  • June 2014
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • March 2013
  • February 2013
  • November 2012
  • October 2012
  • September 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • October 2011
  • September 2011
  • June 2011
  • May 2011
  • April 2011

▼ Blog Authors

WebSphere Peformance - Alexandre Polozoff's Point of View

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

Follow up on Proactive Application Monitoring and setting thresholds

polozoff 110000N2A2 | | 8,872 Views

A few days ago a few colleagues contacted me about my article on proactive application monitoring.  They're building some templates for monitoring applications in the cloud and they had some questions specifically around thresholds for many of the metrics I had listed.  For example, one of the questions was around datasource connection pool utilization.  Is it reasonable to set thresholds for warnings if the connection pool was 85% utilized and critical if it was 95% utilized?  Likewise, similar questions around CPU utilization and would a warning at 75% and critical alerts at 90% be reasonable? 

 

The answer is, (drum roll please) it depends. 

 

No two applications are alike.  There are low volume, rarely used applications that may never get above 2% connection pool utilization.  Conversely, there are high volume applications where the connection pool can be running at 90-100% utilization.  Better metrics to watch (via the PMI metrics) are (a) how many threads had to wait for a connection from the connection pool and (b) how long those threads had to wait.  Both of those metrics directly impact the throughput and response time of the application. 

 

Same with CPU utilization.  Some organizations like to run their servers hot over 90% utilization because they have spare, passive capacity they can bring online.  Others like to run at less than 50% utilization because they want to have spare capacity in an active-active modus operandi. 

 

Setting useful thresholds depends on understanding the organization's Service Level Agreements (SLAs) and the application's Non Functional Requirements (NFRs). 

  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification

Send Email Notification

+

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry