1. At times it does. I have had to modify some of the default monitor definitions for the Unix based machines.
2. We use SiteScope in conjunction with Performance Center to monitor AIX, HP-UX, Windows, Sun, and RedHat.
My only complaint is the fact that I can't have the best of both worlds with the install. I can either do a LR install to get the monitoring down to 15 seconds or I can do a regular install to get the reporting and history. I want both!
I have used the commands and the \script.remote to pull some times out of a log file on a Unix machine. We had a small struggle with it due to not using the right shell at first.
I use it comprehensively during the load test runs as well as for Production monitoring. I should add that this tool gives you a little bit of headache when it comes to Production monitoring because of it's outdated GUI as well as some of the limitations with respect to its alerting logic. The other thing I heard is the new versions of Sitescope doesn't support the Classic version which is by far the best weapon in SiS.
Some of the key items I monitor.
1. Basic Monitoring (CPU, Memory, Process, Ping, Load)
2. Weblogic MBeans monitoring
3. Apache Server status monitoring
4. Oracle Database monitoring (Querying V$SYSSTAT and V$SQL views)
4. MySQL monitoring (SHOW STATUS)
5. TCP Close_Waits monitoring (We use a custom perl script for this).
6. Webservice monitoring (monitoring for the response time for specific web service calls)
Making the custom scripts work and to align it with the Sitescope variables can be quite tricky. But I would say it's worth it in that you can literally gather statistics from any component and not rely on out of the box counters.
1. So far, so good. However, I am a SiteScope newbie and I easily get suspicious about some of the data it returns. Unfortunately, the official HP documentation is very poorly written and often I have to guess how to make some features work.
2. We're measuring SAP application and database servers.