How Does PerformanceGuard Work?

I'm Morten, I manage the PerformanceGuard help. I also run my own complete PerformanceGuard system in order to monitor the computers and servers that we use to create and deliver help articles like this one. To illustrate how PerformanceGuard works, I'd like to take you on a short tour of my system. We begin the tour on my computer, and then we follow some performance data from my computer as the data travels through the PerformanceGuard system:

How do the agents know which data to collect?

They get a configuration when they connect to the frontend server. PerformanceGuard administrators set up agent configurations in the PerformanceGuard web interface. You can set up anything from a single general agent configuration to multiple different configurations for agents on different computers.

Do I need separate frontend and backend servers?

No. Technically, the PerformanceGuard frontend server and backend server are services, so they can run on the same computer and use the same database server. For larger PerformanceGuard installations, however, you get a better load distribution if you use separate hardware. See our Hardware Recommendations.

Want to Know More About how PerformanceGuard Works?

For more detailed information, look in the table of contents, for example under Concepts & Terminology.

For the technical details, look in the table of contents under Technical Reference.

If you're a technical consultant or software developer who needs to integrate PerformanceGuard with other tools, look in the table of contents under API.

Search this documentation

On this page

In this section