Splunk AppDynamics Reviews

We use it for performance and transaction trace monitoring. We use it for .Net and the JVM-related work. We look at all the heat maps and the Garbage Collection to see if there are any failures. 

It gives me the ability to trace logs between transactions, for example, a DB transaction or JVM transaction from one hub to the other. I can easily find out where the problem is or where the bottleneck of the issues lies. 

The overall performance of this solution could be improved. The hot-hot infrastructure features could also be improved. If one goes down, the other should pick up automatically. When we patch one data center, the other primary or secondary center needs to be manually started. We need to do a manual sync between the database and the AppDynamics applications.

I have been using this solution for four years. 

This is a stable solution. The only drawback is that it is not a cluster environment and it doesn't have hot-hot features.

This is a scalable solution but we would like more options to hold more licenses. Right now we have 30,000 agents using this solution.

The technical support for this solution is good.

Positive

Before AppDynamics we used a product called BlueStripe that was acquired by Microsoft. 

The initial setup of this solution is straightforward. The deployment is also straightforward because we used some of the provisioning tools to package the software and distribute it. Creating dashboards and fine-tuning JVMs took some time. 

This solution has really helped us to improve some of the performance of the JVMs at an early point in coding.

I would rate this solution an eight out of ten. 

The solution is deployed on-premises and on the cloud. It has a software gate in several legacy software, and they have part of the application in the cloud. AppDynamics is able to deliver cloud information.

We have 774 small cities, and all the cities have agencies who use the system. We monitor all of the agencies. There are eight million consumers who access these systems on a mobile device and millions of transactions per day.

We used AppDynamics to identify gaps and bottlenecks in the software. After that, we were able to monitor the application and the flow of the clients in all the software of the company.

The interface and user experience could be better. New products were built after the analysis of the dynamics. After analyzing the traffic, the bottlenecks, and the problems with the database, it's our job to make sure users in our company have a better experience with this solution. Mainly during COVID, there was a high number of transactions. Today, the solution is much better than two years ago.

After we fixed the bugs and bottlenecks, the quality of the software improved. It reduced problems with queries on the database and problems in the browser and mobile application.

I have used this solution for two years.

I'm responsible for the implementation of the dynamics in my company and installing and implementing the database and all kinds of monitoring using AppDynamics.

It's stable.

It's scalable.

Technical support is good.

Setup was very difficult. It took around one year.

There was a team of 12 people involved in the consultant database administration. I don't know the number in the working directory because each system in the company was the responsibility of only one team. There was a team responsible for the system of transformation.

Implementation was done in-house.

I would rate this solution 9 out of 10. 

I would recommend it for anyone who wants to use it. 

AppDynamics is an application performance management solution. We use it for application monitoring, database monitoring. 

The solution is deployed on public cloud, but the agents are on the servers with the controller on the cloud.

I am a Senior Performance Engineer.

The best feature of AppDynamics is the analytics, which gives us the business insights of the application. For example, if there are any failures, AppDynamics will give us the number of failures and the reason for those failures. 

The solution also allows us to deep-dive into the code by taking us to the line of code where it feels there is an issue.

The end-user monitoring needs improvement in this solution. There are many KPIs that are not available in AppDynamics.

The mobile apps also need improvement. The solution should have an option to aggregate the services based on the header values.

I have been using AppDynamics for 5 years.

The solution is stable. We have been using it for the last 5 years. At the beginning we had a few issues, but now it is serving its purpose.

There is a scope for improvement with respect to support. When you make a service call, they sometimes take time to respond. You then have to follow up or escalate to get them to react.

Neutral

Prior to AppDynamics we were using Dynatrace.

The initial set up of AppDynamics is easy.

You are required to purchase licenses whether you use it or not. It is not pay-as-you-use.

If you implement AppDynamics, all members of the team should be aware of what it does and how to use it. If only one or two people are aware of this, the solution will not serve the purpose of improving application performance or in finding and fixing the issues.

I would rate AppDynamics a 7 out of 10.

We use AppDynamics for monitoring application performance, end-users, and infrastructure. The product has analytics covering all these areas. 

We're a large organization, so we appreciate AppDynamics' wide coverage. It may not work great in all areas, but it has broad coverage. We use the same dataset for different use case aspects. That is the beauty of AppDynamics. You can coordinate APM, EUM, and infrastructure through one dataset. 

AppDynamics not so great with cloud technology. AppDynamics works very well with the on-premise technologies, but it is behind the curve in the emerging cloud features. 

The cloud is one area where I think AppD is not that great.

Basic monitoring is the main thing, but nowadays, everybody talks about observability. I'm not sure how well AppD fits into the so-called observability trend. The track-and-trace mechanism works very well with on-premises technologies but not so great with the cloud.

Cloud monitoring is becoming more critical. Competitors can pose a big challenge. AppDynamics is a top product, but they need to maintain the same trend in the cloud area, where it's not that great.

We have been using AppDynamics for four to five years.

AppDynamics works reasonably good.

AppDynamics is scalable.

We use the SaaS model, which is the most common way to deploy AppDynamics. Infrastructure setup was not an issue as we chose the SaaS model. We don't have any concerns in terms of infrastructure. 

We only needed to deploy the agent, which was relatively straightforward. I wouldn't say it was effortless, but it wasn't complicated, either. We made a package to automate the deployment, which worked pretty well for us.

I don't know the details about the pricing.

I rate AppDynamics eight out of 10. 

We are currently using AppDynamics Database Monitoring on-premise but we are migrating to the cloud.

We are using AppDynamics Database Monitoring to understand where the long queries are, and how your applications are performing against the database. You can actually see whether it's a database issue or if it's an application issue. Additionally, you can run explain plans against it, to see which queries need to be optimized.

I have found some of the valuable features of AppDynamics Database Monitoring to be once the installation is complete, you are able to quickly start receiving metrics, which is great. The user interface is also very user-friendly.

I have found it sometimes a bit difficult to trace the transaction all the way through to the application. I'm not sure if that problem is on the database side or on the application side, but that would be something that I would like to be improved. The traceability from the application to the database, sometimes, is a bit of a challenge. If you're using AppDynamics, with the Java agent, for instance, you need to be able to trace it through.

I have been using AppDynamics Database Monitoring for approximately six years.

The solution is highly stable.

We have more than 100 people using the solution in my organization. We have plans to increase the usage of the solution in the future.

The installation is easy. It would take about an hour and a half maximum to do the installation because you need connectivity to the database itself. It was more a connectivity problem than it was an actual APM installation issue.

I am able to do the installation myself.

There is an annual cost for the use of this solution.

I would recommend this solution to others.

I rate AppDynamics Database Monitoring an eight out of ten.

We use AppDynamics Database Monitoring to identify high spikes in critical data, which helps us better understand when applications stop responding or are not responding well.

The solution can be deployed on-premises or in the cloud.

Data monitoring is the most valuable feature.

The price of the solution has room for improvement.

I would like the solution to be more customizable to meet our client's requirements.

I have been using AppDynamics Database Monitoring for two years.

I give the stability of AppDynamics Database Monitoring an eight out of ten.

I give the scalability of AppDynamics Database Monitoring a nine out of ten.

The technical support is excellent.

Positive

The initial setup is straightforward. The deployment takes two weeks and requires one architect and one developer.

We implement the solution for our clients.

The pricing is average. I give the price a five out of ten.

The license is paid on an annual basis.

I give AppDynamics Database Monitoring a ten out of ten.

We require five people to maintain the solution.

AppDynamics Database Monitoring only requires users to have a basic understanding of databases.

I use it to solve issues that my clients encounter, such as application slowness. It helps me identify whether the issue is related to the database, server, or CPU memory management.

Moreover, I use it to find solutions and provide recommendations to my colleagues.

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. In essence, it helps us address problems at an early stage. Moreover, it is especially useful in production servers where real users encounter numerous issues.

There are numerous issues that arise during peak times, and AppDynamics makes it easy for us to identify the problem areas and determine the appropriate resolutions. This is how it helps us find solutions effectively.

Regarding improvements, I believe the dashboard could be more optimized. Although it claims to be optimized, I think it should be even more convenient, especially for advanced users. 

Additionally, the documentation can be a bit challenging. It would be beneficial if the documentation provided clear solutions for every problem. In my opinion, the documentation could be improved.

I worked with AppDynamics for around three to four months. I have been working directly with it for the past year.

I use the latest version. 

It is stable, but the only downside is the licensing part. Other than that, it's a reliable product with no major issues.

It is highly scalable. There are no additional limitations in terms of scalability.

In my company, we have around 50 to 100 clients using this tool. Although it can be a bit expensive, it is still being used extensively to solve various problems.

It's straightforward, not too complex. However, it requires proper learning to effectively use it.

The deployment process typically takes around one to two hours, depending on the system. Once the setup is complete, we can proceed with the implementation process.

First, there's a need for basic knowledge of OS, especially for Windows and .NET. Additionally, understanding concepts like Dynatrace and AppDynamics, their functioning, and architecture is crucial. These are the key methods involved in the deployment process. If it's a cloud solution, then AWS or Azure are the recommended options. If it's on-premises, then using either Linux or Windows is ideal.

For deployment, we need to focus on event configuration, which involves learning about network events and configuration. Once we understand this, we can proceed with the deployment setup. There is no frequent deployment. In case the deployment is not satisfactory, we may need to learn about Linux and Windows concepts.

I have seen some ROI. 

It is an expensive solution. It's on a yearly basis. We need to pay for it annually.

I have used Dynatrace. The main difference between the two is that AppDynamics utilizes different data mechanisms, while Dynatrace uses a unified agent approach. This simplifies the complexity of Dynatrace, providing more visibility and root cause analysis. In terms of benefits, AppDynamics is more scalable than analytics.

Overall, I would rate it a nine out of ten. 

We use AppDynamics for monitoring purposes to check up on CPU health and application health status.

AppDynamics is used to monitor the health of our applications. If any application is down and linked up with AppDynamics, we can see it on the AppDynamics console. We can identify when a specific process went slow and the exact issue. Additionally, if there is any high CPU utilization or other issues, we can figure it out using AppDynamics.

It is very helpful as we can also make custom alerts in our system for specific issues like high CPU utilization or application downtime. We can even customize the alerts to be sent to a particular email domain for automatic notification, so there's no need to monitor it 24/7.

The monitoring feature is very useful. If you have multiple applications and systems with high CPU utilization or other issues, you don't need to monitor them individually. With AppDynamics, you can get all the information from the dashboard. It's very convenient.

There is room for improvement in the customer support team because finding a solution consumes a lot of time. When there's any issue, we need to reach out to the AppDynamic support team to get some idea of what the issue is. If anything is out of scope, we need to escalate the availability. It can be more dynamic because we need to go to the support portal to raise an incident, and it's time-consuming. Also, the resolution time takes longer than expected. If there were live support from AppDynamic's point of view, it would be really helpful.

I have been using this solution for the last three months. I am using the latest version.

AppDynamics is a stable solution.

It is a scalable solution. We have some support guys, admin guys, and other people using AppDynamics. In our organization, we have around 15 members using it.

The initial setup is not that complex. It is easy. I would give it a four out of ten. The deployment took two to three days.

An in-house team did the deployment.

I used some other tools, like Sterling Integrator, for EDI solutions.

Overall, I would rate the solution a nine out of ten.