Reviews (1-4 of 4)
SiteScope was mainly used by the I.T. Infrastructure team. However, other internal teams did make use of its specific alerting capabilities as SiteScope is very customizable.
The main business problem that SiteScope addressed was "how do we get alerts, notifications, and/or emails when there are true issues in our environment?" SiteScope was flexible enough to satisfy being the answer to this question. I will say this, that it, in and of itself, was not the sole solution, but rather a piece of our overall greater monitoring and alerting solution.
- Custom monitors with custom thresholds, timing, polling, and many other configuration options.
- Custom ways to alert and notify. Of course you have email and text message capabilities, but SiteScope also allows for specific messages and variables within those messages to be sent out so that your alert is data filled and you can know exactly what is going on and why you received that specific alert.
- Monitor templates for quick and rapid deployment of one's standard set of monitors. Easy ability to "copy" and "paste" monitors so there is no need to re-create from scratch.
- Scripting. SiteScope also allows for custom scripts to be called from specific alerting triggers. This allows for HUGE and POWERFUL customization and automation through SiteScope. You can easily have scripts that "take action" on a specific alert so you don't have to!!
- Very easy to use in my opinion. Learning curve is very short and you can master this system fairly quickly for all of the depth of customization that it offers.
- SiteScope does not monitor certain physical components. For example, SiteScope cannot monitor things like power supplies failing, failed hard drives (it DOES monitor disk space), array controllers, etc.
- SiteScope does not offer cascading alerting. By that I mean that alerting is an all or nothing type of thing. It does NOT offer this example of a kind of configuration: alert tier 1, if no response, then alert tier 2. It is only capable of alerting 1 to many emails. So if you are looking for that type of cascading logic to alerting, you may want to look elsewhere.
- There is no mobile application that I know of. So, you are limited to email and text message alerting unless you link it to some other application that does that sort of thing.
SiteScope is definitely well suited in an HP server environment. It is also well suited for virtual server environments. It is also well suited for those who are happy with email and text based message alerting.
It may not be appropriate in other environments where monitoring physical components is critical. Because HP SiteScope does not monitor certain physical components, it does fall short of being able to be a "one stop shop solution" in regard to monitoring. It is not well suited for those looking for logic in how alerts are sent and cascade to other people or groups.
- URL based monitoring
- Remote monitoring for CPU, memory and disk
- Log monitoring
- The Java version to run the tool has issues sometimes with running the application.
- The reporting function needs some improvement.
It is not appropriate for a very large scale environment as the tool has some scalability issues.
- SiteScope emulates users with the use of scripts and without fail it has alerted us to potential application issues.
- SiteScope could be a bit more user friendly.
- The interface is very "clunky" and slow. It is also difficult sometimes to find what you are looking for.
- All the infrastructure monitoring things are preexisting and we don't need to set up anything additional when using HP Sitescope. We have monitors for ps, CPU, etc., for our application.
- HP Sitescope can also run the custom scripts in our servers and send an alert based on the output. For example, we are running one custom script with HP sitescope to monitor large size files and send an alert if they exceed the threshold.
- Sitescope will have logs as well which can then be forwarded to splunk to draw graphs in splunk for the dashboard. For example, ps is very expensive in splunk and it was disabled. So we are sending that stat from HP sitescope and have a splunk dashboard to show the memory of that process over time.
- Sitescope is particularly used for infrastructure monitoring. Other kinds of monitors cannot be set using HP sitescope.
- Sitescope cannot have graphs like splunk which is why we have splunk as well which is an additional cost for the company.
- We can't have a direct regex operations on data inside HP sitescope. We need to have the logs placed as a single log and then do that.
Micro Focus SiteScope Scorecard Summary
Feature Scorecard Summary
About Micro Focus SiteScope
Micro Focus SiteScope Technical Details