Since LoadRunner version 8, SiteScope has been the recommended and preferred model for monitoring application infrastructures when running a LoadRunner test. This is why a SiteScope license is included with LoadRunner. Enhancements are made to SiteScope's monitoring capability, such as the ability to query the VMWare Hypervisor for stats, that you will not see made to the base controller. It is agentless for LINUX and UNIX environments which is important since most organizations will not run Rstat to allow you to connect.
There are some monitors which are easier to implement in the controller, with a few caveats. If you are in the same domain as a Windows host that you want to monitor and you are signed on with credentials which allow access to the perfmon counters on the other Windows host, then you can add monitored elements in the controller quite quickly. If you need a second set of credentials or you are in a different domain then turn to SiteScope as it is setup to handle these variables better. Monitoring ORACLE, on the other hand, always seems to me to be easier from the controller directly, but this is a general exception to the SiteScope Rule. SNMP based items are also easier under SiteScope.
Note, the two tools have been integrated, with the ability for LoadRunner to use SiteScope as a proxy to pull monitored items, since LoadRunner version 8.
James Pulley
Why can we deliver high quality work at such an aggressive price point successfully? We hire for foundation skills, not for tool skills.