PerformanceGuard monitors how well your organization's computers, networks and servers work. PerformanceGuard specializes in how IT performance affects users' ability to work efficiently.
Your organization must have installed PerformanceGuard before you can use this information. Ask your PerformanceGuard administrator if you're in doubt.
PerformanceGuard can help you with many typical performance information needs. Note that this list is by no means exhaustive; you have many other options for finding information in PerformanceGuard.
This is what to do when you want to know ...
You get a call from a user. Her computer is slow — can you fix it, please? The first thing that you want to determine is whether the computer really is slow. If yes, the next thing you want to find out is what slows the computer down.
The Computer Overview dashboard (Dashboards > Computer Overview) has a Computer Event Timeline Widget that makes it easy to determine if a selected computer has had performance problems. If it has, the widget makes it easy to see exactly which problems the computer has had, and exactly when they happened.
The widget looks at events that have happened on the selected computer, and displays them as bubble markers on a timeline. Remember what an event is? It's a threshold violation, for example a response time that isn't acceptable. You can zoom in on relevant events and click the bubbles to view details.
When a user calls you about a problem, you often need to determine the scale of the problem: Whether the user's computer is the only one that has the problem, or whether other computers have the same problem.
The Computer Overview dashboard (Dashboards > Computer Overview) tells you just that. When you look up a computer on that dashboard, its Computer and Neighborhood Status Widget compares the performance of the computer with the performance of other computers nearby.
Click the thumbnail to view an example where the problem clearly only affects a single computer.
PerformanceGuard helps you identify resource-consuming users and processes in seconds.
PerformanceGuard helps you quickly identify your "resource thieves:" processes and users who consume excessive amounts of resources like CPU power and RAM.
- The quick overview: The Processes and Users graph (ANALYZE > Graphs > Combined Bar Charts > Processes & Users) provides the overview in an easy-to-view bar chart format, no matter whether you are looking for resource-consuming users or processes.
- The details: The Process Resources hotspot (ANALYZE > Overview > Hotspots > Process Resources) provides detailed data about resource-consuming processes, and you can drill down to view which computers and user accounts ran a given process.
Do you suspect that something is eating up your bandwidth? Or do you simply want to know if a particular application or location generates a lot of traffic? Would you like to know when traffic occurs? PerformanceGuard provides the answers:
- The quick overview: The Load Overview (ANALYZE > Overview > IP Traffic > Load Overview) is a pie chart that very quickly lets you find the processes that are responsible for the largest amounts of IP traffic. When you generate the pie chart, try to select Type = Processes and Data type = Load (Sent + Received Bytes).
- The details: The Process Traffic hotspot (ANALYZE > Overview > HotSpots > Process Traffic) provides detailed data about traffic-generating processes, and you can drill down to view details about which servers the process communicated with as well as details about which computers and user accounts ran a given process.
- The timing aspect: The IP Traffic by Process graph (ANALYZE > Graphs > Time View > IP Traffic by process) is ideal when you want to check if certain processes generate traffic at specific times. You can view this for all servers, for groups of servers, or for individual servers.
Look at server response times: If many of a server's responses are slow, it is typically because the server's hardware is not able to cope with the amount of work that the server has to do.
The Response Time Histogram displays response times for selected servers.
To view the histogram, select ANALYZE > Graphs > Statistics > Histogram.
The histogram consists of 10 individual bars.
Each bar represents the percentage of replies within a given milliseconds interval.
This way you can very quickly find out if a particular server is potentially overloaded — like the blue one 
in the example image.
The Response Times Versus Load graph (ANALYZE > Graphs > Statistics > Response Time Versus Load) can help you uncover otherwise hidden scaling problems.
If response times increase to a non-acceptable level when the number of requests per second increases, it's very likely the result of an overloaded server getting more requests than it can handle.
In the example (click thumbnail to view image in full size), the gray 
server responds quickly no matter how many requests it gets. However, the response times (horizontal axis) of the purple 
server dramatically increase when the server gets many requests (vertical axis)—a typical sign of an overloaded server that could benefit from a hardware upgrade in order to perform better at busy times.
The PerformanceGuard transaction filters feature is highly useful for monitoring web-based applications.
The Compare Web Activities graph (ANALYZE > Graphs > Combined Bar Charts > Compare Transactions) lets you compare the various transactions under a single transaction filter. That way you can, for example, detect if a specific element of a web request takes longer to access than other elements.
In the example (click thumbnail to view image in full size), it is evident that one of the elements in the web request takes much longer to access than the other elements.
The Traceroute Graph (ANALYZE > Overview > Trace Route > Trace Route Graph) helps you quickly detect any network latency.
A traceroute detects and captures the path that a network packet will travel from a given starting point (a computer that has the PerformanceGuard agent installed) to a specific destination.
While PerformanceGuard detects the route, it will also record the network latency between different routers along the route until reaching the final destination. The results are displayed as an easy-to-understand network map.
The traceroute graph requires that your organization has set up traceroutes. Read more about traceroutes and other similar types measurements in Monitor Availability, Latency and Response Times with Application Ping.
When you're ready for more, simply try out the many different graphs, reports, dashboards, etc. Each of them have matching help, so just click the help icon if you need to know more.
Search this documentation
On this page
In this section