Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Storage Resource Monitor (SRM) > Storage Resource Monitor (SRM) Getting Started Guide > AppStack integration > Investigate a performance issue using AppStack

Investigate a performance issue using AppStack

Table of contents
No headers
Created by Anthony.Rinaldi_ret, last modified by Melanie Boyd on Nov 21, 2016

Views: 8 Votes: 0 Revisions: 3

This example uses AppStack with SRM and SAM An alert has been triggered because an application has entered a critical state. Use Appstack to determine what caused this alert.

  1. Navigate to My Dashboards > Summary to display the All Active Alerts resource.


  2. Move the cursor over the triggering object name to see a snapshot of information about the object. In this example, the SQL application is reporting high read latency across many databases.


  3. Click the triggering object name to display the application details page.

    The AppStack environment shows the infrastructure on which the SQL server depends. The server is up, but one or more interfaces is down, and the LUN that the SQL server uses is in a critical state.


  4. Move the cursor over the LUN icon to show more information.


  5. Click the LUN icon to display the LUN details page. The Performance Summary resource shows the high latency.


  6. Look at the Latency Performance Per Related LUNs on the same page.

    You can see that the related LUN tex-esx-02_Lun13 is also showing high latency. This is known as a noisy neighbor, an object making demands on resources that adversely affects other objects in the same pool.


    In this example, tex-esx-02_Lun13 is a database in query that is not supposed to be running at this time, so you could get with the database team to stop it or investigate if requirements have changed.

Last modified