We performed a comparison between Apica and Dynatrace based on real PeerSpot user reviews.
Find out in this report how the two Application Performance Monitoring (APM) and Observability solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It uses a basic scripting language, which is easy to learn and customize as needed. Compared to LoadRunner, I found writing and customizing code much easier in Apica."
"What I like the most is that Apica can simulate different browsers and different versions of desktop or mobile browsers."
"I like the transcript download feature. And with UI scripting, it's helpful that Apica handles a lot of the backend work automatically. I don't have to tag everything manually, though I can tag elements later if needed. It's really good at recording the steps."
"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."
"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."
"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."
"It is easy for beginners to learn and use Apica."
"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."
"Scalability is great. My biggest concern when we first put it in was the resources that it would take up, network traffic that it might create. But it seems perfectly scalable to any environment. Even on some of our heaviest use servers, it doesn't seem to affect anything."
"This tool helps us gather information from all hosts and services, then cross reference the information."
"Service engineers save a lot of time because they can just go in look at the data and share it with the customer, who has the same view, and say, "Here's an improvement which can be immediately implemented." It's not like a collection of big, multiple findings that are consolidated into one results presentation, then the customer needs to do something. It's more like a continuous performance analysis and improvement process, which is more efficient than those workshops approaches. That's one of the biggest of the advantages that our services team sees because it helps DevOps to focus on continuous delivery and shift quality issues to pre-production."
"In terms of AI, I love the base-lining Dynatrace provides us. It baselines the application over a seven-day period; we have it at the default of seven days. The artificial intelligence is so amazing because it can automatically track each transaction and their response times: how much CPU they use, how much memory, resources that they use. If there’s any deviation from that Dynatrace will tell me like right away. If there’s a deployment and the deployment has increased response time or is taking up CPU or has caused a memory leak, I can say, “Hey guys, you need to look at this, it’s this function on this page in this microservice, in this docker container. You need to go here, you need to fix it, it’s not going live.” It has just increased our productivity off the charts."
"When collecting data with Dynatrace, we saw every single transaction that happened in real-time."
"The most valuable feature is capture of 100% of the traffic. Also, exposure to downstream services, that might not necessarily be new, to everybody who's using applications. It triggers them and captures them and it gives visibility to some pieces that might be forgotten or even obscured."
"The autodiscovery of service intercommunication has saved countless man hours and is dynamically updated when new services are added."
"Triggering gives us warning that system is getting slow and we need to nail down the issue soon, so it does not impact our business."
"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."
"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."
"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."
"We could use more detailed information in the request and response sections."
"When it comes to the way the internal agent is installed, because you can install an application on a server, I would love to see the application Docker-ized. If you could install internal agents using Docker or using containers, it would be easier for us to manage them and spin up internal agents."
"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 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."
"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."
"So far, we have not achieved the benefit of preventing issues."
"The analytics feature provides us some information, but is limited for now. We want to see how we can consume the data further down and have analytics guys look at the datacenter information."
"The con of Dynatrace is that, at times, because it has so much information, it becomes difficult to see the root cause of your problem, and then you have to dig around to find the root cause."
"One thing that would help it tighter integration with DCRUM. It's somewhat difficult to drill down and see everything, but I think that's in the future versions. We just haven't seen that yet."
"The GUI has the most room for improvement. Sometimes, it can be a little cumbersome to find things and be able to create your own views, or be able to dig in and understand where things are."
"Make it easier to define applications. E.g., provide an API for applications defined by REST services."
"Documentation could be improved. E.g., you don't know how to properly use Dynatrace because documentation is almost lacking behind the features being deployed."
"We have had some struggles with scaling. We were on AppMon, and AppMon has its own monolithic drawbacks."
Apica is ranked 45th in Application Performance Monitoring (APM) and Observability with 6 reviews while Dynatrace is ranked 2nd in Application Performance Monitoring (APM) and Observability with 341 reviews. Apica is rated 8.2, while Dynatrace is rated 8.8. The top reviewer of Apica writes "Offers transcript download feature and easy to set up and configure tests but not very user friendly". On the other hand, the top reviewer of Dynatrace writes "AI identifies all the components of a response-time issue or failure, hugely benefiting our triage efforts". Apica is most compared with Datadog, AppDynamics, Apache JMeter and OpenText LoadRunner Cloud, whereas Dynatrace is most compared with Datadog, New Relic, AppDynamics, Splunk Enterprise Security and Azure Monitor. See our Apica vs. Dynatrace report.
See our list of best Application Performance Monitoring (APM) and Observability vendors and best Log Management vendors.
We monitor all Application Performance Monitoring (APM) and Observability 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.