Splunk AppDynamics Reviews

Our primary use for this solution is troubleshooting.

The most valuable feature is the middleware tracking.

This solution is easy to use.

I would like to see improvements with respect to the visibility of the network. It currently provides visibility on the application side, but not on the network layer.

More visibility and granularity would improve this solution. I would like to see accommodation for millisecond granularity, as we only have one-second granularity now.

This solution is very stable, and I believe that it is enterprise-grade. We use this product very extensively.

This is a very scalable solution.

We currently have five users, who are all technical, but it can be scaled to many more.

I would rate their technical support a seven out of ten. Sometimes the queues to get to the concern are long. Then, if the issue is really complex then they need to try it out in their lab before they can create a fix. Sometimes the wait time is based on priority.

I was using Dynatrace before this solution, and I switched due to ease of use.

The complexity of the initial setup of this solution depends on the application that we are going to monitor. Normally, it takes four to five hours to set it up correctly in a normal environment. On the other hand, it can be complex as well. Typically, our turnaround time to have everything functioning would be about two days.

For anybody who is looking into enhancing or improving their application code quality, I would definitely recommend this solution.

I would rate this solution a seven out of ten.

I'd say BTs, and being able to set health goals. Those probably would be the best. Second to that would be being able to monitor what's going on in real-time, this is going to make a big difference.

I think that previously we were more reactionary than proactive. I hope that this is what we can really get out of AppDynamics, the switch to a more proactive stance. Before anybody else knows what is going on, we will know, and we will be able to cut down our meantime to fixes going out, and to identifying them.

Looking at it from the standpoint of a developer, I see the biggest improvement being that it gives the developers more visibility and ownership, it really lets them see what is going on. I feel that this will lead the devs to make better code and better decisions. It will help them be more cognizant of resources, and other things.

I went through the Power User training, and it was kind of like drinking from a fire hose. As a dev, I would like to see something that is more tailored towards us, instead of having just a general quick Power User session. 

I haven't been able to get the full benefit of AppDynamics yet because I haven't had any time to sit down and actually go through production.

I have not seen any problems with the stability. It seems to be very stable.

I have not heard of any problems with the scalability. 

We have used the technical support and it was very good. We had a good response.

We were not previously using a different solution. We decided to invest in AppDynamics because we wanted to move from being reactionary to being proactive, that's really what it comes down to. Instead of our customers calling us up and saying, "There is something going on," now we will know it before they do, and hopefully we will be resolving it before they even notice.

We are looking into also utilizing Database Monitoring. We're still checking that out.

My criteria when choosing a vendor would be the reputation behind them, the product they bring to the table, and of course the pricing. I wasn't involved in selecting AppDynamics but I know that these criteria always play a role in everything.

I would recommend AppDynamics to my colleagues, because the solution works. It really comes down to whether or not the price point works for them.

The most valuable feature is mainly the graphs that it puts together; the JVM, the heaps, the classes that get called, the number of calls from tiers to tiers.

I think the graphs are mainly used by developers to see what happens in production. We don't know; our workloads. We've been exposed to the internet. We don't know what's coming.

I would like, for example, to see something similar to a heap dump; exactly which objects are over there. I'm not sure it's possible or not. This is a challenge.

A friend compares it to JavaMelody, which I think gives them some of the features that they still want that application to be active. I think it's mainly about the number of threads, SQL executions and similar items, at a certain point in time when you look at them. That could be something.

Sometimes, it can be a little bit too crowded; all the screens. Once you put your dashboards together and you know exactly what you're looking for, it's OK. But if you're always trying to find new problems that you don't know about, maybe that's a little bit harder.

I haven’t had any stability or scalability issues; that's good.

I haven’t had to use technical support.

It kind of came my way from the development team. We used to have Confio Ignite, which was pretty good for me. Then we dropped everything, and then at some point, we needed something new, and we came across AppDynamics.

In general, when I’m considering vendors to work with, I look for the quality of the product and the support. I don't want to be offered professional services every time I call in for an issue, because we are kind of self-reliant. Those are the two things I look for.

Initially, I had the internal controller, which was a little bit more challenging, but then we switched to the cloud ones. It's just easier, I guess.

Before choosing this product, we did not evaluate other options.

It's very easy. It's been easy. The dashboard that comes automatically, the mapping with all the services, the externals; those are all pretty good.

I do not use any other AppDynamics solution.

AppDynamics lets you monitor applications and databases and provide a unified view of your infrastructure. You are able to monitor a single point but this would not be useful and with this solution, you would not use it this way. You want to monitor how your application is impacted from the application perspective to the backend, through to the server infrastructure, database, hardware, network, and application labs. It is all able to be monitored by AppDynamics. It monitors all the aspects from the infrastructure up to the user, and the application.

All the metrics are baselines in networks, infrastructure, application, and user experience. AppDynamics offers its own query language. It is called ADQL. You can write code of any kind to do queries and analysis and you can use those within the reporting or other research. Additionally, together with everything which comes out of the box, you can create your own analytic views, analytic reports, and do a deep analysis of the environment. All the values or all the metrics which are gathered are quite powerful.

This feature needs to be properly described to a client, and then the client needs to have a use case. There are some clients which do not need it and some clients who do. It is not for everyone and is dependant on their use case.

I have been using AppDynamics Application Analytics for approximately seven years.

The solution is stable.

We have done large deployments without any issues. It is scalable.

They provide detailed documentation for support.

The installation has to be done by professionals. If the client wants to take control and do it themselves they will have to do a bit of training.

The pricing of the solution is reasonable for what features you receive.

I would recommend this solution to others. However, they have to make sure it fits their use case.

I rate AppDynamics Application Analytics a nine out of ten.

We are a reseller and AppDynamics is one of the products that we sell to our customers.

Our customers use it to gain insight into performance.

The most valuable feature is the end-user monitoring.

I would like to see support for mobile testing and mobile monitoring.

The cost is something that can be improved.

We have been working with AppDynamics for almost 10 years.

We have not had any issues with stability.

Scalability has not been a problem.

We provide in-house technical support for our clients. We have found that AppDynamics is pretty selective when it comes to providing technical support.

The initial setup is not very straightforward, so it takes some time to complete.

Implementing this solution will require some help.

This price of this product is expensive.

Some of our customers are making the transition to cloud-based deployment, which is something that we are helping them with.

Overall, this is a good product and it is one of our top recommendations.

I would rate this solution an eight out of ten.

Monitoring log and statistics using graphs to see how we are monitoring our network traffic, and whether systems are healthy or not.

In real-time, when we have our peak seasons, we can determine if customers are experiencing something that they are not supposed to, such as customer impact on a service being down or not.

The most valuable feature is having our services being available and healthy. We can determine whether or not, at a given point in time, something is wrong. Then, we can dive deeply into the product to see what is happening by troubleshooting, debugging, and monitoring.

Sometimes, it is hard to navigate through and find if something is wrong or figure out where an error stemmed from. I would like AppDynamics to be easier to navigate in.

I have not seen any issues with stability.

I usually don't see any issues with scalability, and we have pretty large servers.

Our environment is huge. Within a season, we have hundreds of thousands of current users.

I haven't used technical support.

The integration and configuration of the product in our AWS environment was easy. AWS made it easy.

I was not involved in the decision-making process.

I would still use AppDynamics now, because I haven't seen another player on the market give us exactly what we want that AppDynamics can't. There are a lot of companies who are doing the exact same thing and trying to put their own spin on it, but there is no reason for me to pick another competitor.

Testing the customer behavior to learn their problems on a website, the heatmap flow, and other information.

• IT department
• Software production
• Test environment
• QA testing
• KPIs of the business
• Heatmap
• An APM

This tool is so good to work with.

For customer journey monitoring: Stitch together complex journeys involving the entire ecosystem (internal through external IT) and multiple stakeholders.

Has helped us to increase customer acquisitions and reduce revenue leakage in the following:

• Conversion rates
• Average revenue per user
• Customer acquisition costs
• Rate of customer churn
• Recurring or incremental revenue
• Renewals and/or subscriptions.

End user experience monitoring, which includes:

• Uptime (availability)
• App response time
• Database response time
• Percentage of transaction time spent in database
• Resource utilization
• Database query times.

Areas which could be improved:

• Integrated dashboard for user
• Application
• Infrastructure
• Network layers.

There also needs to be an option to capture all the sessions for all the users, not just samplings.