"There are several features that are really good. The first one is the flexibility and the advanced configuration that Apica offers when it comes to configuring synthetic checks. It provides the ability to customize how the check should be performed and it is very flexible in the number of synthetic locations that it can use. It allows us to run scripts from different locations all over the world, and they have a really good number of these locations."
"As always, within the IT industry, everybody's always looking to upgrade and update everything else like that. Apica has been one of those things but it's really hard to replace because it offers us the unique capability to see what the customer is seeing. A lot of other ones can do Selenium script and things like that, but there's a lot in Apica that we use right now. We utilize a lot of the scenario options in Apica right now, and there's a lot of other ones that do parts of it, but it doesn't do everything that Apica does."
"We see the benefit almost every day. It allows us to be alerted whenever there is a store that is not responding properly around the world. We do have a network operation center (NOC) who receives these alerts, immediately checking if everything is okay."
"From our standpoint, there are a number of valuable features. The WebHooks are obviously really great. The alert framework is really good and then the reporting and visualizations that you get from the dashboards is good. Those three areas are primarily what my team's focused on in terms of usage from day to day."
"It helps with releases because we monitor them in staging. We can tell if something is critically wrong before it gets into production, e.g., if it was load related or function related and also what was different in the dev stage. It then alerts us straightaway inside of our production monitors once it has been released. Therefore, it has improved how we run our systems since we monitor multiple environments."
"One of the biggest advantages of moving to Apica is the ability get to a hybrid model with the architecture in the cloud and our agents on-prem. We also have access to Apica's cloud agent across the globe. That has changed the way that we have our load testing setup at this point. Previously, it was always internal. Now, with this change in the way it is implemented for load testing, we can test anywhere across the globe and from the list of agents available within Apica's cloud. If I don't have an agent available in a second location, it just takes an email to their customer support, then it is spun up within 24 hours. That flexibility has changed the way that we perceive our load tests, not just in the US, but globally."
"You can tell from the operational space of people who are using and consuming this data that they are more integrated. It is not dependent on one team anymore. It saves a lot of time by capturing and pinpointing the exact problem that is happening quickly. We have moved from getting escalations manually to getting escalations synthetically."
"With the ZebraTester, the ability to have and store dynamic variables, when setting up the monitors, means you can extract that value and use it in a subsequent service call. This is something that has made our lives easier... This is one of the features that I like the most because it helps us in configuring these services, in a certain flow, without the need to re-record the whole thing."
"Infrastructure monitoring is the most valuable feature."
"The stability of the Micro Focus Voltage SiteScope is good."
"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 having to install an application on your desktop to utilize something like ZebraTester is a little cumbersome. It would be nice to see that become a web-based application. Having the documentation a little more accessible, and easier to digest by people who are just learning how to use the framework, especially when it comes to more complex or more edge-based cases would be really helpful to have."
"The initial screen on their dashboard could have a bit more data, but this is a small thing. It could have more data, so we do not need to drill down to a screen behind that initial information. I would like them to get a little better on the user interfaces that we need to go into."
"There are some components of the user interface that are not up to date. Just to give you an idea, today we have web applications that are called single-page applications that are much faster than the old style of web application. If we can move faster into the flow of the graphic user interface, and in a more effective way, it will save us a lot of time."
"Learning the tool has always been a little difficult from a scripting perspective because the framework is proprietary and unique. Once we became used to what it does and how to perform it, then it became easier for my team and me. I would like to see some of the testing steps be part of a more well-known language, like Java or Python. That would be a big improvement."
"The reporting part that we use for our executives needs a bit more customization capabilities. Right now, you can use only the three main templates for reporting. We would like to be able to customize them."
"We have been focused on reducing polling times for synthetic checks. We have gone from 10 minutes down to five minutes for a pretty broad swath, but there is some appetite to reduce that further, which could be an improvement."
"The accuracy of alerts can be improved a little bit. Right now, it's pretty good in terms of alerting pretty quickly about failures or changes in response times. However, what we have seen happen is the number of alerts that we are getting is very frequent, and we would like to tone down the number of alerts. That's the only trouble we have. Apica could tone down those settings because there is no option for us to tone it down to a level that would reduce the alerts to a minimum. As a platform, it does send us good alerts, but it could be improved a bit."
"Alerting needs improvement. It's a little noisy. It needs some better options. Currently, they have an issue, when you set up a synthetic monitor, you can set up where it's monitoring from, a data center that Apica owns."
"The lack of an agent means that remote monitoring requires multiple firewall ports to be opened."
"I would be very interested in having transaction traceability included in the product, to give us a better view of what is really going wrong in a particular method and action."
"Micro Focus Voltage SiteScope could improve by adding more features, such as cloud, APM, and DevOps monitoring."
Apica Synthetic is ranked 6th in Application Performance Management (APM) with 9 reviews while Micro Focus SiteScope is ranked 41st in Application Performance Management (APM) with 3 reviews. Apica Synthetic is rated 8.6, while Micro Focus SiteScope is rated 6.0. The top reviewer of Apica Synthetic writes "Monitors every single touch point that can fail inside a user's journey". On the other hand, the top reviewer of Micro Focus SiteScope writes "Offers agentless monitoring, is easy to configure and reduces downtime". Apica Synthetic is most compared with AppDynamics, Instana Dynamic APM, Dynatrace, Splunk and VMware Tanzu Observability by Wavefront, whereas Micro Focus SiteScope is most compared with Dynatrace, Splunk, AppDynamics, SCOM and Google Stackdriver. See our Apica Synthetic vs. Micro Focus SiteScope report.
See our list of best Application Performance Management (APM) vendors.
We monitor all Application Performance Management (APM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
