Why use SiteScope with LoadRunner?
Posted: April 22nd, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: LoadRunner, SiteScope | No Comments »Disclaimer! I’m not doing some sales talk here to get you buying the product nor getting paid for writing this post; just sharing my opinion on the usage of the tool with LoadRunner. Anyway, Sitecope comes together with LoadRunner in every DVD copy the vendor issued. It is part of the additional component of the LoadRunner product (look under “Additional Components” in the installation). SiteScope 8.5 comes together with LoadRunner 9.0.
1. LoadRunner may not haveas much monitors as compared to SiteScope. So with SiteScope, you can use it to enhance or compliment the existing monitors in LoadRunner. E.g. you can use the URL monitor to determine if the server is alive while during the load test instead of just seeing errors occurring.
2. SiteScope provides additional monitoring feature for Unix flavored OS by using HTTP, rlogin, telnet and SSH as compared to only rstatd in LoadRunner. rstatd is restrictive as it utilizes a dynamic port. This is especially problematic when you have port clearance to deal with as you will not be able to determine the ports being used. Also, rstatd only provides basic monitoring information for the Unix box. By using telnet, rlogin and SSH, we are able to customize the type of monitoring information we want from Unix by amending the commands issued to the Unix box, such as sar and vmstat.
3. SiteScope provides a centralize monitoring which allows deployment of monitors easily. This is achieved through creation of templates which also allows the standardization of monitor data across all load test project easily. Standardization can still be achieved in LoadRunner, but it is done via manual additional or Standard Operating Procedures (SOP).
4. If you are working in one single environment, it makes things even simpler as the SiteScope server will become the main central server to monitor the environment. All you are required to do is to ensure that port 8888 (default) is accessible from LoadRunner to SiteScope.
I’m still experimenting the different ways that I can capitalize SiteScope with LoadRunner and will update you in future if I’ve found new stuff along the way. Currently, looking at Linux speciiffied Would like to hear from you too if you have other ways of maximizing the usage of SiteScope!
Leave a Reply