Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
With complex networks consisting of cloud, hybrid IT, virtualization, storage area networks, and so on, multi-faceted IT issues can be difficult to pinpoint and diagnose. When an issue surfaces, for example a badly performing application or server, the investigation can take significant time to locate the core issue. The problem could be in storage, network connectivity, user access, or a mix of resources and configurations.
To investigate the issue, create troubleshooting projects with the Performance Analysis (PerfStack™) dashboard that visually correlate historical data from multiple SolarWinds products and entity types in a single view.
With Performance Analysis dashboards, you can do the following:
For SAM, the possibilities are endless for application analysis and hybrid environments:
Want to learn more? See the SAM Administrator Guide.
The following example shows you how to identify a root cause for a Windows Server 2012 application performance issue. In this scenario, the application performance has degraded to the point where users encounter slower responses and access. As you review the Windows Server 2003-2012 template dashboard, you find triggered alerts. These alerts notified your application owner, who escalated the issue to system and network administrators.
Rather than digging into the alerts and multiple Node Details pages to troubleshoot the issue, create a new troubleshooting project to investigate the issue.
In the Orion Web Console, select My Dashboards > Home > Performance Analysis.
This opens the Performance Analysis, or PerfStack, dashboard to build charts and graphs using metrics pulled from monitored applications and servers in the Metric Palette. Each chart can hold multiple metrics to directly correlate data.
In the New Analysis Project, click Add Entities.
Entities include all monitored and managed servers, applications, devices, services, and more in the Orion Platform.
Select Entities and click Add selected items.
To get started, you need to locate and add the Windows 2012 application in distress. In the search field, enter Windows to get a list of all monitored nodes, component monitors, and more with Windows in the name or type. Expand and select Types or Status to filter the list.
From the list, we find the application monitor watching Windows Server 2003-2012 Services and Counters. Select and add to the dashboard Metric Palette.
Interested in all associated nodes, applications, servers, and more to this selected node? Click the related entities icon. All related entities display in the Metric Palette providing more options for metrics possibly causing issues.
Select the Windows 2012 node to view and select metrics to drag and drop onto the dashboard. You can drag them into the same chart to compare values between metrics.
To start investigating, pull a series of metrics for the IOPS throughput for the server. For this scenario, add the following metrics to investigate latency and connectivity:
The charts and graphs display with data and alerts for the Last 12 hours of metrics.
Add more metrics from the virtual and storage layers to investigate and confirm any bandwidth spikes.
For example, add metrics for the IO latency from the virtual and storage layers to locate issues:
Analyzing the data, the issue looks to be a noisy neighbor. Basically, another server, service, or application is consuming higher bandwidth, disk I/O, CPU, and other resources causing issues for this specific application.
This information gives your network and system administrators a direction for further investigation and resolving latency issues. To resolve, they can reallocate resources or move the high-consumption application to another location.
Click Save and give the project a name.
The project saves as a dashboard with the selected metrics in the set date and time range.
When saved, the URL becomes a sharable link. Copy and share the link to the saved dashboard in tickets or emails sent by the system and network administrators and the product owner. They can access the link to review the gathered data and troubleshoot.
After reallocating resources and making network changes, reopen the dashboard to verify changes and new usage trends for polled metrics.