This is an expansion of the previous post Perform the steps logically; it’s an overview built will keep you on focus of the things to do during monitoring setup. Read the rest of this entry »
Let’s dive down to the detail configuration of Windows System Resource monitoring. First, I’m leaving out the configuration in Controller and will be discussing only the monitoring setup outside of LoadRunner. If you want the details for configuring in LoadRunner, I encouraged you to refer to the Controller User Guide that comes along with the installer. (Which I may discuss it if feasible in future).
Second, concepts and fundamentals must be aligned before proceeding and these, can be found in the previous posts, “How does the monitoring work in LoadRunner?” and “4 Monitoring Implementation Models”.
To monitor Unix System Resources, you will require rstatd. The rstatd daemon is a server that returns performance statistics obtained from the kernel. The rstatd daemon is normally started by the inetd daemon.
In most cases, rstatd is already configured and started from inet. Therefore, you should verify if the rstatd daemon is already running using rup command. The command should report various machine statistics, including rstatd configuration. Run the following command to view the machine statistics: Read the rest of this entry »