What is our primary use case?
We use the solution for agentless monitoring of network and systems infrastructure including Linux and Windows, multiple versions, and multiple "flavors".
The primary use case is for meeting the needs of basic level monitoring of multiple devices across a single-site network.
When accompanied by APM tools from the Micro Focus stable, Sitescope provides a useful "bottom-up" (technology --> Application) view of performance and availability. Other APM tools provide a "top-down" (i.e. a user-centric view) of performance and availability.
How has it helped my organization?
Sitescope is a very useful solution for agentless monitoring. I must emphasize 'agentless' as this is its biggest advantage as well as disadvantage. Sitescope makes it easy to monitor key aspects of performance, availability, and capacity by collecting metrics.
The aim of Sitescope is to help reduce downtime and provide information to help maintain performance. It does this reasonably well.
Sitescope though is better thought of as a component within a wider Micro Focus-based ITOM/AIOPS solution rather than as a solution in itself.
What is most valuable?
VM monitoring is pretty good showing good visualizations of how VMs are operating within the context of all the VMs running on the same hypervisor.
The ease of configuration is an advantage as Sitescope simply requires entering a host's credentials and a connection protocol (e.g. SSH, FTP, script, WMI, etc) in order to begin collecting and graphing raw data.
Alerting is basic but functional as a standalone product but provides an additional dimension when used alongside Operations Bridge (which is expensive).
What needs improvement?
Most modern-day solutions in this area include both agentless and agent-based monitoring in the same package. The lack of an agent makes for a simple installation and relatively simple configuration, however, in these days of highly-distributed computing resources Sitescope is missing a number of critical features.
1. The lack of an agent means that remote monitoring requires multiple firewall ports to be opened. This is often a problem when connecting multiple sites. It also makes cloud implementations less attractive too.
2. As data must be "pulled" from the system being monitored, there is a reliance on a performant network and a well-specified Sitescope server.
Sitescope scores well for basic simplicity and it integrates well into other products within the Micro Focus software family - e.g. Operations Bridge.
For how long have I used the solution?
I've used the solution for five to ten years.
What's my experience with pricing, setup cost, and licensing?
If you already have other Micro Focus products, especially the testing tools, then you may already have licenses for Sitescope. Licensing is (typically for Micro Focus) very complex, so speak to your account manager to check.
The setup cost is minimal if you already have the hardware and that's reflected in the functionality.
There are some great pre-packaged monitoring templates known as "solution templates". These are excellent kickstart ways to accelerate implementation - however, be aware that some of them are licensed separately.
If you're considering Sitescope as your sole or primary monitoring tool, I suggest you take a look around - there are better options for you.
What other advice do I have?
Sitescope has been around for many years - since 1996 in fact. Over the years, it has become a highly stable solution. Now though, as Micro Focus now owns HPE Software (who in turn bought Mercury Interactive from where Sitescope came), Sitescope is but a small cog in a very large AIOPS engine.
Disclosure: I am a real user, and this review is based on my own experience and opinions.