Splunk AppDynamics Reviews

The most valuable feature is being able to trace and follow transactions through a complex environment.

It improves production troubleshooting, it improves pre-production performance testing and it improves our development quality, because they can find and troubleshoot performance and quality issues prior to testing.

I would like to see cross-tier, transaction tracing across applications.

It's been fairly stable. It has been fairly solid.

Scalability is an issue. We are pushing the product to its limits on our current hardware allocation, so it's hard to fault the product for that.

We constantly use technical support. It’s pretty good, depending on the nature of the challenge we're having. Sometimes it can be a little difficult getting answers but I think they're still doing a very good job.

We were previously using another, competing product and we re-evaluate all the products on the market regularly.

Initial setup was fairly straightforward. At a large scale, it is incredibly complex but not because of the product itself. The product itself is relatively straightforward.

We evaluated Riverbed, AppDynamics, Dynatrace, and New Relic; that was pretty much it.

We chose AppDynamics because of ease of use for the end users, as well as a relatively compact footprint, as far as the required infrastructure to host it.

We don't select a vendor; we select a product. The vendor needs to meet certain minimum requirements, of course, but ultimately the product speaks for itself.

As always, do your homework. Know everything about the industry that you’re playing in. Know who all of your options are and pick the solution that's best for you.

It's providing massive value for a relatively massive investment, as well, but it is proving itself to be easier to use and therefore more widely adopted than previous solutions. That has been a huge relief to all of us who have been doing APM for years and have wanted to spread that around the company wider than just a small set of analysts.

We are using a little bit of AppDynamics EUM and Analytics.

Performance is the most valuable feature, especially the tag and follow, which has to do with multiple JVMs and diaries. Also, getting to know when you hop into different segments and trying to figure out where this is actually happening, and then that too, if it is happening to the backend. That is the key and that helps.

Server Monitoring has saved us time. We have issues that previously took days to solve, become resolved quickly. Once you know what's your normal, you know your anomaly. That's the key.

We have our own challenges because the amount of JVMs we are dealing with. But still, this is really helpful in trying to analyze a lot of our issues with certain types of JVMs. Not necessarily out-of-memory errors, but a few memory leaks, and a few applications that had third party JVMs that got leaked. Had I not known this, it would have taken a long time to solve these issues. There are ways to find them, but it takes more time.

One area that needs improvement is application integration. They do have it now, but that has to be improved. What happens is, right now, we cannot deep-dive into it. Four years back, I requested application integration. It took four years get it. At least it is there. The thing is that it has to improve. That's it.

Stability is good. I mean, we had issues. I have been using APM for four years, so I know where it was, and now where I am I know, so I'm so happy with it. It's much improved.

Scalability, it's good. It has challenges too, because I'm dealing with a very large setup. Scalability is definitely there, but now with the new features that are coming out, with a backend, it definitely will be better.

I am happy with technical support.

There were initial setup issues on both sides. I don't want to complain and it's not fair to do that, but now, if you look at it, it's reasonably stable, but every upgrade is a challenge. I mean, software is like that. Especially with the amount of changes they are making. The only thing about AppDynamics is they release quickly. Hopefully, they know you cannot keep up with this pace. A big enterprise, cannot handle that many releases like that. It requires a lot of coordination to upgrade to a new release.

And the biggest thing I wanted them to do, is to not require agent upgrades. That means every agent must be recycled. Someday they will push the agent from the controller with automatic upgrades. Something has to happen like that. Hopefully that will happen. That is my next ticket.

Use it, and when you use it, use it regularly. If not, don't use it at all. You won't get the benefit unless you use it properly on a regular basis, so you know what normal looks like. You need to know how this thing looks, so that you know your anomalies and can resolve issues quicker.

I use AppDynamics Database Monitoring to monitor application performance.

AppDynamics Database Monitoring's dashboarding is its best feature.

AppDynamics Database Monitoring would be improved with more support for microservices architecture.

I've been working with AppDynamics Database Monitoring for one year.

AppDynamics Database Monitoring is less stable than Dynatrace.

AppDynamics Database Monitoring is scalable.

The initial setup was easy, and deployment took around two days.

We used an in-house team.

AppDynamics Database Monitoring is widely used, so it's given us some ROI.

I recommend choosing Dynatrace over AppDynamics Database Monitoring as it's easier to use. I would rate AppDynamics Database Monitoring seven out of ten.

Ability to identify end user performance issues and drill down into root cause to improve MTTR and application availability.

Reduced MTTR and put us on a trajectory to be more focused on the end user experience. Provides monitoring more around business processes versus just servers, applications, etc. E.g., with complex systems, where a business process passes across multiple applications, the business needs us to monitor the heath of the process, not just a segment of the application.

• Business transaction capturing
• Analytics
  

Needs more integration with applications suites, like Oracle Enterprise Server or BMC Remedy.

More than one year.

What we do in general is analysis on the application side. When we have slow SQL requests we jump on the database monitoring to see, for example, the total time the request has been pending in the database. We can solve SQL requests by their pending time. 

The explain plan is the solution's most valuable feature.

The database monitoring is quite simple.

An improvement could be if the monitoring was able to be summarized into something more clear and simple for people who don't have the technical skills on the database side.

The solution needs to have some prepared dashboards on the database. When we use AppDynamics we have a lot of screens and we have to jump from one screen to another. It would useful is if, on the database, monitoring required merely a click on a button and then you have the monitoring dashboard that you can display for easy access.

I've been using the solution for three years now.

The solution is very, very stable. We haven't faced any bugs or glitches on the system.

The solution does not offer good scalability. It's quite technical, but basically, when we have to monitor one database we have to check if our Java program allows for the amount of monitoring we need. If it doesn't, we'll need to restart and get more database agents and perhaps spend more money to scale.

We don't have a lot of users on the solution on the database monitoring portion. It might be as many as 20 people. They are software engineers and database admins.

We only use the solution occasionally when we suspect there are problems on the database side. It isn't used daily.

We create a lot of support tickets with AppDynamics. We've been using the solution for a few years now. The support is quite weak. There's a lot of back and forth, however, eventually, they give us decent solutions.

We didn't previously use a different solution.

The initial setup is very straightforward. It's not complex at all.

It only takes about 10 minutes to create the user on the database.

The initial setup is actually done in two parts. The first part is to create the user on the database that we want to monitor. This part is done by the database teams etc. The second part is handling the AppDynamics controller. This part is handled by me or someone on my team.

A company only needs one person to handle the maintenance once it is up and running.

We handled the implementation ourselves.

I'm not in charge of licensing. I don't know what the costs associated with it would be.

For me, the first recommendation I would have to other organizations considering implementation would be to have a person or people who have good skills on database monitoring. How AppDynamics works is basically just monitoring the metrics that already exist in the databases. These metrics are really technical metrics, so a company has to have some people that are really specialized in reading them. They need to have a good database administrator or database analyst in place.

I would rate the solution seven out of ten.

Monitoring and mediating the risks are the most beneficial features.

Before we moved the code to AppDynamics, we had to compare the agile process and also had to make sure that they're following the standards. Thus, monitoring the actual quality of work in AppDynamics is the most valuable feature to us.

It would help to maybe have a more graphical interface and more user-friendly graphics. I don't think that Java is so adaptable since the marketplace has improved a lot. Thus, they have to improve in terms of the GUI.

There was not that much downtime experienced.

It is scalable across the board. We have implemented it across our company. It will meet the needs of the company, going forward.

The other team took care of the support. I am only a DBA but as far as I know, I haven't heard of any issues as such.

The setup is very simple. To be honest, it is pretty straightforward. They sent a team to help us out with the implementation. From the database side, we worked with the product team members to put in the database and also for the infrastructure laydown. It was straightforward.

It is a good product and I would highly recommend it.

Whilst looking for a vendor, the most important criteria is honesty. I don't want to waste time, so I want honest feedback. We don't want any lame excuses such as, there is no patch or that they are still working on it and so on. Thus, honesty is most important.

If you talk about the Application Analytics, we have different systems, all kinds of integrations from the application space, I have so many systems to integrate. For business transactions, I have more than 20-25 systems. Without getting these analytics, where there are bottlenecks in the system, and where I see an issue, it's very difficult to track and debug.

If I spend a long time debugging an issue, I'll see more revenue loss; more bad customer experiences, which impacts my business’ revenue. What we do with the analytics, we have installed AppDynamics, instrumentation, and everything. At any point in time, if we want instrumented data, we just go back and take it, pull up the analytics, and see what it is throwing up. It's drilling down; showing snapshots of everything; bringing together different systems. It's really helping us. It's easy. It doesn’t take too much time and does not impact any performance on the servers. It's not too complicated of a system to understand. It's very easy, more readable to the users; just go over and grab the snapshots, and say, “Hey, here is the issue.” Just go over and fix it, drill down to see what is causing a problem.

Recently, it helped us discover some security issues, which now we see have been there for few years. There is a loophole in the security system. It was taking way too long. I've been running millions of transactions, and we were not able to discover it. But with AppDynamics, we just started monitoring. It simply brought our attention to analytics, saying “Hey, here it is. It's behaving weird.” We were able to drill down and we found a few servers that were behaving weird. We're able to develop a fix. There was previously no way to discover the issue. If it’s working fine, it’s working fine, but those few transactions were taking a long time.

It's really helping. We're so happy. That's why we want to understand, see how much further we can leverage it. It is not just the analytics, but how can we take it to the business; how can we turn this into a business-centric tool, as well as application monitoring. We have seen some of other vendors and it's really awesome.

As of right now, we are just going with demand-based monitoring, when there is an issue, a performance bottleneck or something. However, we are also exploring how we can set the continuous monitoring system, where we can get more of the analytics, see more of the long snapshots and see what the actual problems are and where, even if we're meeting customer experience very well, we can go beyond these customer expectations by improving some things. These analytics are helping us to build on those areas.

In the Business iQ, I don't know how much they’re trying to grab it, but we want to see more of the transaction, each and every area, from the users’ perspective to the end of the transaction, from the user to the network. There could be situations where the user is sitting in some other region, trying to access a system that is located in US data centres; there wasn't a problem from that. I want the transaction details from the data centre to the back end systems, and the back end systems to third-party integration. I should be able to correlate different transactions; all the pieces onto the dashboard, saying, “This is how it turns out.” That's what we are actually looking for.

We want a single monitoring tool. We don't want thousands in there because right now, I am discarding analytics monitoring tools. It's difficult to compare. Each tool has a different perspective but if you have a monitoring tool across everything, that’s where we see scope for improvement.

We want to explore more. We just started. We were on a different technology. We just started, so we want to explore it more and then see how it scales up.

It works as usual. I'll give an example. We have seen some other application monitoring systems from other vendors I won’t mention, where, as soon as we implement the monitoring system and start the application, the monitoring itself kills the performance, which is severe and so complicated in solutions. AppDynamics is just simple to put in. The agent shows a zero impact on the application servers, which we use Oracle. It's really good.

We've never used technical support, because it’s easy, super easy. We have reached out a few times just to understand more of how much we can use it, but not on the performance which AppDynamics is causing. There were misconceptions in the beginning that maybe it is causing a problem, but even after turning it off, the problem did not go away. We later realized it is not the problem. There were some interpretations about it later on, but it was pretty good.

We were previously using a different technology.

I was not involved in the setup. We have separate team for that. We are the architects. We requested they put it in the first place but there is an infrastructure team. They do the setup. The guidance which AppDynamics provided was really helpful.

I definitely would recommend AppDynamics. After looking at the snapshots, I think I see we're using less than 5-10% of what AppDynamics is capable of. I would definitely recommend exploring not just the analytics and the Business iQ, but I would also encourage you to show the network stats on the Business iQ, which is very important, very critical, and is very difficult to find out those things. Definitely those are really helpful.

We do not use any other AppDynamics solutions, but we were exploring the Business iQ at a recent AppDynamics conference. There was another application, End User Monitoring. I wanted to see that piece of it. It looks pretty interesting and I want to see how it takes.

The most valuable feature is the standard APM agent for Java and .NET. We always find bottlenecks in applications with these agents.

We've seen tasks the end users have to do on a daily basis that used to take 30-60 seconds been improved to take under two seconds, based on reports and recommendations we have written based on AppDynamics. The developers had been troubleshooting this specific issue for months before we installed AppDynamics. We installed AppDynamics, found the bottleneck, wrote the report and gave our recommendation within four hours.

In general, AppDynamics is by far the easiest APM tool to use. The biggest room for improvement is related to maintenance of the solution. A centralized upgrade of agents is sorely missed.

We have been delivering services around AppDynamics for two years now.

We have not encountered any issues with deployment, stability or scalability. However, it can be confusing deploying the analytics agents; this had to be planned carefully.

AppDynamics has hands-down the best technical support I've experienced, and I've worked with all the major APM vendors.

Initial setup, if you choose the SaaS solution, is very straightforward and well documented. Choosing the on-premise solution is more complex, but not any worse than its competitors.

I cannot discuss our customers’ ROI. I would advise to get as many APM agents as you have application servers, to start easy with EUM, and grow the EUM as your website/app grows. Don't do analytics at first, if you don't have a clear business case for it.

We have delivered, and deliver, services related to Dynatrace and HPE. AppDynamics is, today, the solution that is easiest to deploy and gives the quickest ROI.

Just try it. AppDynamics has a free, 14-day trial. If you don't have the needed staff or knowledge, talk to one of AppDynamics’ partners.