We performed a comparison between AppDynamics and Grafana based on real PeerSpot user reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: According to user feedback, Grafana is the preferred option when compared to AppDynamics due to its open source features, customization abilities, and visually-pleasing graphs. It also boasts flexibility in integration with various tools and datasets. While AppDynamics has more features, Grafana is seen as more adaptable and user-friendly with moderate pricing and flexible licensing.
"Autodiscovery of application topology, based on real user traffic."
"The most valuable feature of the solution is the fact that it is very easy to use, making it easy to implement...It is a very stable solution."
"The most valuable feature of AppDynamics is its ability to track the transactions between different applications."
"Error analysis in the troubleshooting sections go straight to the point."
"The solution helps us save a lot of time on certain tasks."
"The real user monitoring helps us evaluate our customers' real experiences, which is valuable as an eCommerce company."
"We previously had an operations team continuously monitoring applications. Now, they just have set things up and our developers can monitor, view, and act on them, accordingly."
"This solution not only provides answers but also provides sensor data. This allows us to quickly resolve issues that developers may take a long time to solve."
"Collaboration: Shares data and dashboards across teams."
"The most valuable thing was that it had a good visualization tool."
"This solution provides valuable insights into the health of our infrastructure in real time."
"The most valuable feature of the solution is the UI dashboard because we need to create a dashboard on Grafana to monitor our data."
"The dashboards are very easy to work with."
"It gives us the visibility we need. I like that when we add deployment markers or release markers, we know exactly when an issue arises. For instance, if there is an increased usage of CPU, we can link it directly to the deployment that might have caused the issue. It increases productivity and observability. We can now easily tell when a certain issue arises. It's way easier to debug because it can point you to certain things based on these markers, and we can debug easier."
"Kubernetes could help us to better visualize the trend of our data by recording and displaying our history over a chosen duration, such as the last 30 days."
"Plugin: Connecting Grafana to multiple APIs of leading monitoring tools and alerting tools."
"I would like to see more of a unified platform. They're very, very new on the server side, machine agents. I want them to be more mature in this area."
"Its resiliency can be improved. We're told that the best we can do with an on-prem solution is to have a hot standby that requires a manual switchover. So, it is a do-it-yourself Ikea model of maintaining data consistency between two servers, without having low balance or failover considerations for an on-prem solution."
"AppDynamics is agent-based, so some customers are reluctant to install the agents in all their production environments. It would be helpful if they had an agentless version. It covers applications on the server, but the solution is weak on the network side. The agent is not deployed on the network components, so it cannot provide complete information about issues on the network layer."
"I would like to see something that lets me set real dollar figures, not just to outages, but to the solutions as well... when I'm looking at problems and have found a problem that I know I need to address. I could flag it off and have AppDynamics estimate how long a person would have taken to find that without it. That would give me a lot of leverage for justifying the existence of APM, which I really need."
"AppDynamics' modules and hardware resources are very high."
"SQL statement monitoring"
"Maybe some more CPU power or something like that could be an area to improve."
"They need to improve the consolidation of agents for the agent's installation process."
"The service dashboard is very hard and needs improvement."
"There is a need for improvement in automating daily monitoring reports, especially when alerts are triggered due to system downtimes or fluctuations."
"Grafana need to improve the logging functionality."
"The solution should include online support."
"The solution has room for improvement with a better API to help automate the construction of the dashboards easier."
"If there was an issue on one node, we couldn't drill down and see all the issues on other nodes."
"Its interface could be more accessible."
"Its UI features to create charts can also be improved. Some features could have a link to the documentation."
AppDynamics is ranked 5th in Application Performance Monitoring (APM) and Observability with 154 reviews while Grafana is ranked 6th in Application Performance Monitoring (APM) and Observability with 38 reviews. AppDynamics is rated 8.2, while Grafana is rated 8.0. The top reviewer of AppDynamics writes "Very good real-time monitoring capabilities, deep problem diagnosis, and transaction mapping". On the other hand, the top reviewer of Grafana writes "Agent-free with great dashboards and an active community". AppDynamics is most compared with Dynatrace, Elastic Observability, Datadog, Splunk Enterprise Security and ITRS Geneos, whereas Grafana is most compared with New Relic, Azure Monitor, Sentry, Dynatrace and Datadog. See our AppDynamics vs. Grafana report.
See our list of best Application Performance Monitoring (APM) and Observability 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.
