Micro Focus Voltage SiteScope Review

The GUI is cumbersome, and it requires a Java client

What is our primary use case?

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

How has it helped 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.

What is most valuable?

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.

What needs 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!  

For how long have I used the solution?

More than five years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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

How are 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.

How was the initial setup?

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

What about the implementation team?

We implemented using an in-house team.

What's my experience with pricing, setup cost, and licensing?

Easy to setup, but I’m not able to recommend this product any longer because there hasn’t been any real investment in enhancements that allow for cloud or container monitoring.   Apparently they no longer charge for solution templates and I’m not sure how they price the tool.  They’ve changed it over the years from “points”, metrics, and monitor count.  Not sure how they are selling this tool these days unless it’s to customers looking for an agentless onprem tool with no need to monitor new technologies.  

Which version of this solution are you currently using?

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Micro Focus Voltage SiteScope reviews from users
...who work at a Comms Service Provider
...who compared it with AppDynamics
Learn what your peers think about Micro Focus Voltage SiteScope. Get advice and tips from experienced pros sharing their opinions. Updated: March 2021.
474,038 professionals have used our research since 2012.
Add a Comment

author avatarAmr-Younis

Hi, SiS pricing model has changed and now (may be a couple of years) it is not priced per monitor and templates are not charged for as well

author avatarCarl Brahms Jr
Top 10Real User

Ok, I’ve revised my review to reflect what you’ve shared. Thanks.