PerformanceGuard is a software solution that monitors your IT systems and tells you if anything is wrong.
- Wrong means, for example, unusually long response times, congested networks, unusual resource usage or unusually large amounts of traffic.
- Unusual typically means something that crosses predefined thresholds, for example if DNS response time goes above 50 milliseconds.
| Info | |||||
|---|---|---|---|---|---|
| |||||
|
PerformanceGuard reports exactly what's wrong, and which of your organization's locations and computers are affected. You can get alerted when something looks like it could go wrong, rather than when it has gone wrong. That way you can fix potential problems before they become real, and users begin to get affected.
Let's look at some examples:
details| Page Properties Report | ||
|---|---|---|
|
| Page Properties |
|---|
Get Fast ServiceYou call your insurance company to file a claim. The call center guy who answers your call looks up your details in a database. Yesterday, that database began to respond slowly, but PerformanceGuard detected it, and the insurance company's IT division fixed it. That's why you get a quick response from the call center guy today. Your time is precious, so you're a happy customer. Without PerformanceGuard, every caller would have waited an average of 30 seconds longer today. For a call center that gets 1000 calls a day, that would have meant a total of 8½ hours' extra waiting time, which in turn corresponds to an entire working day that could have gone to waste. |
| Page Properties |
|---|
| Page Properties Report | cql | label = "Test" and space = currentSpace()
Get Fast ServiceYou call your insurance company to file a claim. The call center guy who answers your call looks up your details in a database. Yesterday, that database began to respond slowly, but PerformanceGuard detected it, and the insurance company's IT division fixed it. That's why you get a quick response from the call center guy today. Your time is precious, so you're a happy customer. Without PerformanceGuard, every caller would have waited an average of 30 seconds longer today. For a call center that gets 1000 calls a day, that would have meant a total of 8½ hours' extra waiting time, which in turn corresponds to an entire working day that could have gone to waste. |
| Expand | ||
|---|---|---|
| ||
We recommend that you read about the PerformanceGuard web interface (that's the web-based user interface where you view performance data and configure PerformanceGuard). If you're new to PerformanceGuard, also read our Get Started guides for administrators or users. If PerformanceGuard has already collected some performance data for you, we also recommend that you read I Want to Know ... (it's about how to interpret your performance data) and When Is Performance Good or Bad? |
| Expand | ||
|---|---|---|
| ||
For a guided tour of a real PerformanceGuard system, see How Does PerformanceGuard Work? Also, take a look at Concepts and Terminology. For the technical details, look in the top menu under API & Tech Reference. |
| Panel | ||||||
|---|---|---|---|---|---|---|
Search this documentation
On this page
In this section
|
...