SiteScope Review
The GUI is cumbersome, and it requires a Java client

Primary Use Case

I have used SiteScope for over 10 years as a synthetic monitor for everything under the sun. 

Improvements to My Organization

The Monitor Templates functionality allowed us to spin up monitoring with .csv files pretty easily.  

We ended up using the "script" monitor the most, because the canned monitors didn't always do what we needed. It was easy enough to use, and the ability to use regex to monitor output in alerts and thresholds made the product very configurable.

Valuable Features

For host monitoring, agentless monitoring requires no installs or special permissions, just a regular user account on the host and firewall access to SSH, WMI, NetBIOS, etc.  

DBQuery, URL, and Web Service monitoring were also valuable until we started using another tool for real transaction monitoring. Now, we rarely need to setup synthetic monitoring for applications, because we have actual user performance data.

Room for Improvement

It was a great tool for a long time. My go-to tool for everything. However, something happened at HPE years ago and investment in the development of the tool seems to have tanked.  

They have not kept up with browser security requirements or advances in GUIs, they switched to a corruptible database architecture instead of text config files, and the licensing is way more expensive than other tools that do the same thing (like LogicMonitor). Monitors have bugs that sit unfixed for multiple versions (file age and SOAP/XML Web Service monitors). The GUI is cumbersome, and it requires a Java client!  

Use of Solution

More than five years.

Stability Issues

Yes, some conditions trigger false alerts which is pretty difficult to recover from. The worst thing you can hear is that every monitor is opening a ticket from one server. Another admin built flood limits on the alert receiver side to prevent this issue from creating too many tickets to handle.

Scalability Issues

I did not see many issues with scalability which did not involve host infrastructure limits.

Customer Service and Technical Support

There are some very capable HPE/Micro Focus engineers on the forums, but overall opening a ticket was usually a waste of time for us. Most of the time we would have to figure out the problem ourselves through debug logging. Often, we would have to restore from a backup, in the event the monitor database would get corrupted.

Initial Setup

Easy to setup and teach other teammates how to create monitors, templates, etc.

Implementation Team

We implemented using an in-house team.

Pricing, Setup Cost and Licensing

Expensive licensing model. You have to pay for their "solution templates". Other tools do not charge you for knowledge-based monitoring bundles. Solution templates are just included in their product, or offered free as configurable add-ons.  

Disclosure: I am a real user, and this review is based on my own experience and opinions.

Add a Comment

Why do you like it?

Sign Up with Email