Splunk AppDynamics Reviews

We use this solution to help reduce incidents in our production environment by providing usage and performance metrics, application dependencies like databases, .net services, caching, and much more.

This solution has helped us to reduce the number of incidents in our Production environment and improve the performance of applications.

The uptime of our critical applications went up, and it has enabled us to set new SLA metrics.

This solution makes it fast and easy to diagnose performance issues and exceptions/errors in application coding.

After a major incident, root cause analysis is conducted and, most of the time, we understand what caused the incident and how it can be prevented from happening again.

The Web Dashboards are also very useful and sometimes can really prevent incidents before they happen.

Upgrading application and machine agents on a large scale is a nightmare; we cannot push upgrades through the platform, meaning, manual upgrades each time a new major release is out. Each time we have a new major release, we need to do a Rollout.

The Mobile AppDynamics app is a "Thing of the Past". AppDynamics should evolve the features presented by it; redesign it. Dashboards are impossible to read, and drilling down issues through it is impossible.

The worst part is that the AppDynamics SaaS Environment has a lot of downtimes, and AppDynamics, despite our efforts, does not give us any feedback on these downtimes/incidents.

Update: 04/2021 (4 years using AppD)

We still face outages in out SaaS controller... The feedback we get about each outage is really limited, and especially without sharing any improvement plan.

We have been using this solution for more than two years.

04/2021 Update (four years using AppD)

Poor stability of the SaaS environment.

Scaling this solution is fast and user-friendly.

Support for agent problems is accurate and fast.

Support for SaaS solution stability is very poor.

Setup was fast and straightforward.

We used a vendor partner team for our deployment, and we found them to be very skilled.

We have seen ROI in less than twelve months.

Our use case for AppDynamics is helping customers with performance problems and applications.

What I found is that there is a lot of room to develop things in it and to connect to other tools like IBM.

An area that has room for improvement on the CR and ERP would be the addition of monitoring of the internal solution. For example, you can monitor the day-to-day and everything in the transactions with AppDynamics, but there's also a lot going on in the kernel itself that you cannot monitor. The automation needs to improve as well. As it stands, a lot of customization needs to happen before you can use AppDynamics.

We have been using AppDynamics for four years. 

AppDynamics is scalable for medium-sized companies, but it is more difficult for enterprise companies.

The AppDyniamics technical support is good. We haven't had any problems with them. They answer very quickly.

The initial setup was not really straightforward, but it was also not complex.

We handled the implementation in-house. The installation is not really an issue. You can install AppDynamics in an hour, but the configuration takes a long time before you have everything configured.

Return on investment for most tools takes a long time. Even then, I don't know if it's really the tools giving you a return on investment. Tools point to a problem, but they don't point to a solution. Your engineer needs to come up with a solution.

When deciding whether or not to go with AppDynamics, first take a look at what you need to monitor and what the value of the monitoring is. There are a lot of things that an organization may need to monitor, like, for example, if I have the power system on, I may need to monitor the microcode and the window system. However, AppDynanics doesn't monitor these kinds of things. There still need to be a lot of patches implemented in order to improve performance. Also, these tools give a false positive that the performance is wrong, but then only adjust one parameter in the microcode.

Yes, IBM APM, and Dynatrace

I am using this product to monitor all microservice environments. I check all services and performance issues and implement some alerts and dashboards. We are also monitoring all applications that are not in a microservices environment. They are in a WebLogic environment. So, we use it to monitor WebLogic applications, Tomcat applications, and microservice applications that are running in the OpenShift environment or Kubernetes environment.

AppDynamics is in the middle of our monitoring environment. It is connected with all other monitoring applications. It helps us to check all the errors and performance issues because all our alerts, related to the performance of our website or backend applications, are implemented through this. So, it is one of the most important monitoring applications.

The ability to check parameters for microservice applications is most valuable. It is important for me. I can manually create new business transactions for applications and individually monitor business transactions. 

I can also use a lot of extensions. It has a lot of extensions to monitor other third-party applications, such as NoSQL applications, memory cache applications, Kafka applications, and Couchbase applications. It is very useful. We are also using the end-user monitoring site to follow all end-user activities. It is important for us to check the errors on the customer site.

We constantly need to improve our alert mechanism because we get a lot of false-positive alerts. These are not real errors. In addition, for end-user monitoring, sometimes, we are not able to catch all user activities. Because of not being able to follow the user activity from the start to the end, we are missing out on the performance issues.

I have been using this solution for two years.

It is good when you constantly check it. In our company, we use AppDynamics a lot. We are monitoring all applications with AppDynamics. Therefore, all the time, we need to check if there is something that needs to be improved and all related applications are okay. For example, our database might be getting bigger and bigger. If you are used to checking frequently, it is okay. I have prepared some procedures for checking all AppDynamics components. It is not hard for us.

In terms of the users, mostly the DevOps team is using this solution. On the development site, we have more than 100 users because all developers on the test system are checking all the processes.

It depends on the issue. It is mostly good. Sometimes, we had really difficult issues, and the support team was really trying to solve the problem, but it took a bit more time.

Its initial setup is easy. We are installing all the components on the same server. We don't need to install another database. It is included in its own database, so all the configurations are on just one server site.

As compared to other applications, its price is moderate. Its price is neither very high nor very low.

I recommend doing a central configuration for agent installation. It is really easy to run when we are upgrading our agents. The standard installation is good in my opinion.

I would rate AppDynamics an eight out of ten.

We deployed our agents on the cloud for a Kubernetes application. We get the hardware details from the Azure and AWS monitoring. We import those matrices into AppDynamics and we see all of those details, along with our application performance detail, within the AppDynamics solution.

We are not using machine agents because we are making use of the Azure Monitoring and get the matrices from there.

The most valuable feature is the application performance. We have details such as CPU utilization and memory utilization, which we make use of to finalize the amount of CPU power or memory that we should allocate to our ports.

AppDynamics is easy to implement if you follow the documentation, and the documentation that they provide is good.

The agent deployment could be simplified by, for example, adding a GUI.

Correlation should be improved.

End-user monitoring should provide options for data collection, including using a JavaScript file or using a network request in the case of a mobile application.

It should automatically upload the mapping file.

I have been using AppDynamics for a few months.

This seems like a stable product and we plan to continue using it.

AppDynamics is scalable.

I would say that the support is 50/50. It is not very fast and there is definitely room for improvement in terms of support.

When we were installing it for the first time, it took us some time and we had some issues. One issue we faced was because we deployed all of the agents on all of the ports together. This created some problems, so the next time, we deployed it one by one. This is the process recommended by AppDynamics but somehow, we missed that part.

After that, it was stable and it continued working without any issues.

For the whole application, we were able to deploy in less than two hours.

We deployed it ourselves, although we had a consultant available online who was available for assistance. We didn't face any issues, other than deploying all of them at one time.

One technical person who has the details and information on the ports should be present. They need to know all of the commands that are used to deploy the agents.

I would rate this solution an eight out of ten.

We are using it for performance management. We are using its latest version. Right now, we are in the adoption stage. We are going through the training process, and slowly we will start using it. Initially, a team of 50 people will be using AppDynamics. Our goal is that all teams use AppDynamics so that we can benefit from it. 

With AppDynamics, we were able to identify where the database query was taking more time, that is, whether it was taking time on logical IOs or physical IOs. So, it helped to track down a lot of issues. It is also giving proactive alerts that help us to narrow down issues much quickly and fix them before they start impacting our customers. It has also been quite helpful when we want to show to our management or customers how this application helped.

From the performance management side, I like everything from business transaction work to tracking. On the database side, we can get a lot of insights from the database. On the server monitoring side, it helped us a lot to find out some of the issues on the VM side because VMs were creating a little trouble for us.

At this time, we don't have much visibility on the virtual environment, monitoring, and all other things. We have visibility only for database monitoring, and we have noticed performance impact when deploying database agents on the database server. We got to know this from AppDynamics support also that we should not deploy database agents from the database server. When agents are deployed on the same server and the database is monitored from there, we are not getting database server metrics. Therefore, we don't have those insights, and sometimes, we struggle because of that. They can improve this functionality so that we do not have a performance impact, and we can deploy anywhere. This would help us a lot.

In terms of end-user monitoring, currently, it is not working for us because there are some complexities. It is a little complicated, and it takes a little bit of time to understand where you need to make changes. It would be very helpful if they can provide some template designs for end-user monitoring.

When our servers are running on VMs, we don't get many insights from the VM side. I don't know whether it is possible to have visibility beyond the database, server, and application and whether there are some features where we can deploy AppDynamics on VMs as well. Such functionality would give us more control over storage, VM, OS, and database. It will also provide complete visibility of our hardware and software.

I have been using AppDynamics since 2019, so almost one and a half years.

It is stable, but I noticed that a lot of times, the controller takes more time to load metrics, which impacts our productivity because we have to spend a little bit more time on this. I don't know if it is something internal or something that needs to be done from our side in terms of licensing and deployment.

I am satisfied with their support.

It is easy. We need to configure a few transaction detection rules. It also works well out of the box. For deploying for other customers, it has export and import functionality, which is good.

We were exploring some open-source tools, but then we decided to go for an enterprise-level tool because we have a lot of customers. We have a cloud as well. That's how we decided to go for AppDynamics.

It is a very much recommended tool. It is a really good and helpful tool for productivity.

I would rate AppDynamics a nine out of ten. I love this tool, and I don't have any issues with this tool.

We use the product for enterprise-level monitoring, everything from application to database monitoring. The product will tell you everything. It will show you at the code level where the issue is. For example, the solution will analyze a database and it will tell you which of the CPUs are taking more time to execute, showing exactly where the issue is.

It has allowed us to find issues fast and resolve them.

It would be helpful to have a dashboard and artificial intelligence for error detection and correlation for future releases. 

I have been using the product for six years.

It is a stable product in my experience.

Their support is really good.

The setup was straightforward. It is easy to install, it took about half an hour. 

We deployed the solution ourselves. We used one technical person to analyze the solution for deployment but then we did not need any technical assistance afterwards, it is pretty straight forward to understand. 

The networking monitor function could be better, we are not getting many details from it.

It is easy to use and not difficult to configure. I would definitely recommend the solution, I have been working with it for the last five to six years. It's a really good product.

I rate AppDynamics Database Monitoring a seven out of ten.

We are a solution provider and I am a presales engineer. AppDynamics is one of the products that we implement for our clients and have experience with.

At this time, I'm using it for training purposes, for the team.

The features that I like best are the dashboard and Business Journey.

AppDynamics is dealing with a lot of products and technologies, so we need to have clear documentation.

The community support needs to be a little bit better.

In the future, I would like to see the inclusion of better programming language options. This would allow for wider use, and make it more versatile.

I have been working with AppDynamics for about nine months.

AppDynamics is stable and we haven't faced any bugs.

As we are not an AppDynamics end-user, our experience with technical support is different. At the same time, from a support perspective, I have dealt with the AppDynamics community. I would say that support from the community is good enough, although it is not amazing. I think that community support needs to be a little better.

We did not work with another similar solution prior to AppDynamics. We are a Cisco partner, so we keep moving forward with the same technology.

The first time I deployed AppDynamics wasn't very easy because I didn't have much experience with Linux. However, aside from the Linux-related issues, I found it totally easy.

The deployment is really quick, taking just two or three days. However, we need more time for configuration. If the deployment is good then the configuration will take about one more week.

We do the implementation in-house. We have three people who are working with it.

AppDynamics is a good product and I totally recommend it. Once you feel that you have the full journey for your end-users and you are tracking them, it's awesome. Overall, I am very happy with this product.

I would rate this solution a ten out of ten.

In terms of our use cases, we monitor cloud instances and application instances. When we do performance testing, we monitor all the metrics, like server-side metrics, as well as the client-side metrics. If it is a browser with real user metrics, mobile user behavior kind of things, we'll monitor it as well. 

Whenever the application crashes from user behavior, we can easily simulate the error. We are happy with this feature and find it to be valuable. 

In terms of improvements we would like to see, we want to understand what the battery consumption metrics are whenever a user is viewing something in an app. It would be really helpful for us if we could get those details levels.

I have been using AppDynamics for the past four years.

We use on-premise, cloud, and public versions.

The stability is quite strong. We never experience any downtime. The only thing is that sometimes the agents get stuck where CPU memory metrics will not be recorded. Once we restart those agents, it will work as usual.

I am satisfied with support. We have a dedicated team that works whenever required. If we have any issues in any of the systems, we will send that email to them and they respond immediately. Their response is quick.

I would rate it a seven out of ten. 

Whenever a user uses the device and does a transaction on his phone using some of the apps we want to know how much battery consumption it is taking. We want to understand those level of metrics.

I would definitely recommend this solution. The reason being that it gives more information than we generally need. Whenever we create automation or performance scripts and we want to understand where exactly the crash report is happening, this tool would give more information. Dynatrace is also another tool that gives more information.