Splunk AppDynamics Reviews

The most valuable feature is real-time performance monitoring of my production applications; being able to determine within just a couple of minutes, whether or not my applications are having a problem; and being able to correlate that with issues that my customers report on.

We use it pretty widely across the company. In my particular group, where we've been able to get it situated for all of our .NET and related applications, we've been able to really improve our time to resolution on incidents. We've been able to better institute root-cause analysis for these incidents that we've been having. Whereas before, we were essentially a black box. Customers could say that they were having issues and we would not be able to independently correlate those reports with actual production problems. Now, we have much greater visibility from top to bottom, in terms of the web page and the server level.

We have the database monitoring component, as well. We can take a look and see whether we were having blocking on our database at the time, without needing to engage our database administrator. That also improves our time to resolution.

One of the things that I would like to see is a little bit more ease of use with regards to the analytics component. I know that's new. At a recent conference, there was a session for hands on with analytics that I signed up for. I planned to look at that a little bit. Otherwise, it's been a little bit of a black box to try and get started with our existing infrastructure.

I know that they're moving towards a lot of the things that I would like to see. For example, slightly deeper integration of the database monitoring that's already in place and being able to, a little bit more easily, correlate that to the calls that my web service is making. My applications, in particular, are very, very, very database heavy. Being able to see that more closely linked would be nice. The latest version of the controller has already started moving in that direction.

Being able to use analytics in the way that it's advertised; there's still a gap for me personally, in terms of where we are now and what the capabilities of analytics are. I would really like to see that made a little bit more transparent.

These are small, quality-of-life issues.

The stability of the product, generally speaking, is good. The worst problem that we have with it has to do with firewall rules and making sure that our agents can reach out to our SaaS controller. Once we get that taken care of, we have that data within just a couple of minutes. The stability incidents that we have on the controller level are very rare; it's available most all of the time.

Scalability is pretty good. We're able to on-board new applications and make sure that we get those correlated up very, very quickly. We are actually moving to a full CI/CD stack, which will be integrating our ability to install and upgrade AppDynamics agents seamlessly, without us having to do it manually, like we do right now.

I use technical support all the time. Usually it's user error, stupid user tricks; I'm pretty good at those. There are definitely a couple of times where we've discovered that there's a bug in the agent or the controller.

We also have bi-weekly calls with our technical contacts, as well as our sales contacts. If we're having a problem, that can be escalated up, very quickly as well.

We were not previously using a different solution. It was actually one of my manager’s directives. I actually was with a separate team at Expedia called The Global Customer Operations Center. They had it set up for all of the call centers. If you call 1-800-Expedia, you'll get routed to one of our call centers and they use a set of applications that is supported by this team. It was a situation where users would call up and say that they were having problems, and we weren't able to repro it. They got AppDynamics set up and there was actually a session at that conference that they gave about all of the ways that they're using AppDynamics.

My manager moved to this rather old team at Expedia and one of the things she brought with her was AppDynamics. She was already in the process of getting that set up for that team when I followed her to this other team.

I was not involved of the initial setup of the controller, but we do have several applications that we're on-boarding at this time. Essentially, that is part of our go-live for any of our applications now: “We have this new component coming up. Do we have AppDynamics? Is it reporting?” We refuse to go live on any application until we know that we're reporting that data up through AppDynamics. That is a critical component of our ability to go live on any of our applications.

There weren’t any other vendors on the shortlist at the time. We were pretty much sold on AppDynamics. My manager, Diana, is a very, very big fan of AppDynamics. I feel like it really fits well into that niche of real-time, usable, easy-to-learn application performance monitoring. When I got started in GCO to begin with, it was already there and I knew I couldn't screw it up by going in and poking around. So, I went in, poked around and learned a lot about the application we were supporting; where the problems were; and what we could do about it very, very quickly, within a couple of weeks of my coming onto the team. Things like that all add up into us being pretty dedicated AppDynamics customers. They've got a really good relationship with Expedia, in general. We're very happy with them overall.

In general, the most important criterial when selecting a vendor like AppDynamics is ease of use, both with regards to setup and expansion; for example, on-boarding new applications. For me, personally, that low barrier to entry, in terms of becoming familiarized with the product, understanding how it works, seeing where the benefits are for us and our use-case; I think it was extremely compelling.

One of our sister organizations has a WSO2 Enterprise Service Bus instance. They were using the good old stare-and-compare method of making sure that their services were up. They would start their Java application and go stare at the log file. That was how they knew it was running. They didn't have any visibility into how much traffic it was taking, whether that was normal, what their normal call profile looked like. As part of our own evaluation of WSO2 and their Enterprise Service Bus, we asked this team to install AppDynamics on their servers. They came back and said, "How do we get our own?"

Basically, my advice – to people who are looking at better visibility for their applications; better knowledge of how their customers are using their product; knowing whether your application is up or down is one thing but knowing how it gets used can be something else entirely – is, "See if you can get yourself a trial of the controller and some help installing your agents the first time, and then you'll wonder where you've been your whole life without it."

As a general rule, though, AppDynamics is something that we really can't operate without; even in the case of when we had a pretty big network outage earlier this year, where we weren't able to see the controller from our desks. That was sort of like operating with a big, black blindfold on. It's amazing how much we have come to rely on that instant, up-to-the-minute visibility that we have for our applications.

We have other tools like Splunk to help us dig through the logs, but even that doesn't provide the same level of detail that AppDynamics does. I don't really know if there is another product that does. For me, it's a pretty easy win to say that AppDynamics is certainly one of the most important components for us in supporting production environments.

We are not currently using any other AppDynamics products. We're researching how to implement that. Unfortunately, a lot of our applications are legacy. We've got some classic ASP that we haven't moved to .NET. There's a little bit of upgrade hurdle cost with regards to getting the EUM integrated with these classic ASP and related applications. As we start moving towards upgrading and replacing these products, that's something that we're looking at; making sure that we integrate the EUM with it. It's not something we've done yet.

It focuses on a much better idea of the end-user experience, of what they’re doing. We're not using end-user monitoring per se, but it gives a much better idea of what it's feeling like for them. We have all these hundreds of different URLs and web pages they can end up going on; be able to track all those individually and separately, and have it all be automated. We don't need to go through and say, "Hey, track these ten pages." It just loads it up, all on its own. It picks up new transactions that come through, new pages. When they release new code, we don't need to go through and manually assign what needs to be monitored.

AppDynamics allows us to quickly determine where a problem may lie. If a customer complains about slowness there may be hundreds of different servers that could be responsible for the slowdown. AppDynamics allows us to quickly determine where the choke point is. For example, is it a slow database call, a slow webservice call, or maybe a slow method that needs to be re-written by our engineering group? It can take less than a minute to determine where the fault lies. This means we spend less time trying to determine what the issue is, and more time fixing actually it.
The depth of monitoring that AppDynamics offers also means that we are aware of issues very quickly. It is very rare for our customer support to alert us of issues before AppDynamics already has. Most things are fixed before a customer even has a chance to call into our support center.

I’d like the mobile app to scale out a little bit better. There have been things that are missing from the mobile app that show up in the desktops. Also, there are some usability things in terms of, how quickly can I get down to active alerts? How can I filter off of those, especially when we have a lot of applications, a lot of tiers, a lot of business transactions? The mobile app gets the job done but it's missing a lot. I often times feel it is easier and faster to just pull out the laptop, boot that up and go through there instead of the mobile app.

The mobile app needs a little bit of work, making sure that the feature set that is available on the desktop, that we can copy it over and do the same thing on the mobile app.

Stability’s been good. We are using the hosted environment and sometimes it's a little bit slow, but most of the time, it works pretty good.

Scalability is kind of mixed. One of the problems that we come from is how they do the pricing. It's always per node or per module, but a lot of companies, including mine, know that often times you'd rather have a lot of smaller server instances instead of a few bigger ones. However, because we get charged per instance, all of a sudden that gets much, much more expensive as opposed to doing fewer large server instances.

I did open up one incident and it was resolved. I didn't really like the answer that came back, but it worked.

We weren’t really using any solution at all, and that was our problem. We had high-end server monitoring tools and log management, but we never had a true APM in the past. So, we looked around a bit, and this is the one we chose.

There weren’t any other vendors on the shortlist, as far as I know. I came in after most of those decisions were made. I wasn't involved with that initial discovery phase.

The most important criteria when selecting a vendor like AppDynamics are uptime, usability, and making sure it has the features and meets the needs that we have.

It works great, especially if you don't have anything that's currently doing that type of monitoring. It works great for doing what you need, when you want to track response times and error rates; and especially being able to dig down to individual transactions and see the actual call methods. That's amazing when you’re trying to debug issues and figure out what's causing slowness. So, we love it. It works well.

We’re not using any other AppDynamics products; just the APM right now. We've looked into a few of the other products, but the way our environment is laid out, it doesn't really make financial sense for the time being.

The most valuable features are basically the customer experience that it provides, and the deep dive that it gives; the overall dashboards, and then the strength of the dashboards, so you get a single pane and can see across the platforms.

It's much easier to set up and manage than the previous products we've had. It is basically a lot cleaner. It's just simpler to set up, simpler to manage, and gives a much better picture of anything else we've had.

The biggest thing that we need is on-prem synthetic monitoring. That is probably near the top of our list of things that we want, and actually need to have put in place. A lot of our business comes through intranet only, so a SaaS product can't provide that. We really need an on-prem synthetic monitoring solution.

I haven’t rated the product higher basically because of the synthetic monitoring piece. We started discussions with AppDynamics probably about two years ago now. Even at that time, they were saying on-prem synthetic monitoring was going to be coming. We had our hopes up really high for that, and it seems like there's been some feet dragging there. From our side, we're a little bit impatient about it. That's probably the only reason why I haven’t rated it any higher.

It is very stable. We haven't had any problems with it going down, crashing, getting upgraded or anything like that. It's been very stable.

Right now, we're using it for a very small piece of our environment; running it in a pilot right now. We've had it for probably about six months in production, so it’s relatively new. From a scalability perspective, we do plan on expanding it out, and it seems like it would be easy to do, we're just not mature enough at that point.

It's been very good. I personally haven't been the one opening the tickets, but whenever the people that work for me have opened up tickets, they've gotten quick responses. It's been very easy to get things answered and any fixes put in.

We currently, and actually still have, the APM product by CA, and it has been kind of a headache to manage from day one. Any sort of maintenance on it, any sort of upgrades on it were always a pain to get done. That, in combination with the strengths of what AppDynamics provides from a dashboarding perspective, a metrics perspective, business transactions perspective, it's a lot stronger than what we're getting out of CA. The strengths combined with CA's maintenance and headaches, it was kind of a no brainer for us to want to switch.

With initial setup, everything was actually relatively simple. It went pretty smooth. There is somewhat of a learning curve from our side of things, but overall it was simpler than other things we've had to deal with.

We didn’t really consider any other solutions. We did some pretty extensive research when we went with CA, which was basically only four years ago. Once we saw AppDynamics out there, a little bit more mature than when we were first looking at products, and we saw there was a front runner and leader in the industry, it was kind of a no brainer. We didn't really shortlist anything else when we wanted to go away from CA.

For me, the most important criteria when selecting a vendor like AppDynamics is the strength of the company and the strength of the product. Is it at the top of the charts for Gartner? A clear leader: It seemed like they were a vision leader in the industry, so that was one of the driving forces.

I really don't have any negative things to mention about it. It's been all positive. Depending on how the environment is, it can be a bit pricier than other products. The benefits that you get out of it seem to outweigh the costs, from what we've seen so far.

We've also got AppDynamics’ End User Monitoring piece, and we're evaluating the database agents.

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.

One of the most valuable features has been the ease of use that really fuels adoption in our organization. Other solutions that we have used for APM were not as user friendly, and frankly it was just really difficult to get people to use the tools.

The dashboards have been straightforward; easy to set up, really, for the most part.

It's made it easier to collaborate across teams; be able to have the same data immediately in front of you just by sharing a URL.

It could be a little more flexible in configuration on the back end. The design is geared towards specific goals, and they've done a great job with those. A lot of times when I'll ask a question, "Can we make it do this? Can we make it do that?", the answer is just, "No. Sorry, we don't support that at this time." And I get it, that's a good model for them to have, but I always have a wish list of things as I'm working with the tool.

I come across little things all the time, and I just file a ticket with AppDynamics to raise a feature request. So, I don't keep track of them, I just document it, and fire and forget.

I’ve been impressed with the features that they're adding and the direction that they've been working, a lot of which I wasn't aware of. License management, for example; being able to just give a certain number of licenses to an arm of the organization and say, "Here. Here's your licenses, do whatever you want with them." That really pushes the ultimate administration of the product out without having to "micromanage", if you will, and worry about giving them the key to the server. We are not currently using that. As far as I know, it's not released yet, but I was excited to see that. That was one that I brought up with support along the way.

I am impressed that they continue to develop and improve, and it's not a stagnant product by any means.

We have a controller that's pretty overloaded. We haven't run into any issues, though, with the AppDynamics.

Their technical support's been very responsive. They don't always have the answers that I want, but they're responsive, and help us find solutions where they can.

We didn't know that we needed a new solution. We had a solution. Another department wanted to look at AppDynamics. We looked at it and said, "We're already doing that, but if you want to bring it in and test their claims of greatness against what we have, go for it". We brought them in, and we said, "Let's buy that.”

Initial setup was very straight forward. We didn't even use technical services for our implementation.

It could be cheaper. It's a little cost prohibitive. There are so many features that also show a lot of value, but it’s not always easy to justify the cost.

We did not look at any other vendors. We weren't shopping, really.

In general, when I look at solutions, first of all, the product has to be top shelf. It has to be number one. That really drives us: "What is the product going to do for us?" In the vendor, we look for a vendor that's going to be around for a while; that we feel is going to be stable enough to support us into the foreseeable future. And then the support model, technical support; the ability to get into the technical details with us when we have questions. All of those things.

Having implemented without the help of professional services, we were capable of doing that; it went very smoothly. Involve, even indulge, AppDynamics in being a part of the implementation process, and having the planning and discussion around it. We wanted to go more rapidly than that would allow. Therefore, we kind of short-circuited that process, and jumped right in, which was good, but I think that there's value in having folks who have done it a lot look at where you're going with it, and give you some pointers. We've had to "course correct" a little bit on a few points as we went, and they might have been smoother along the way, had we just gone through the enablement and initial process.

It’s a great product. We're happy with it.

Nothing is perfect, so a perfect rating would be unattainable, but they’re pretty close to that. They're really great.

We like being able to actually see how long it actually took. You can look at the back end, and you know how long the server thinks it took, but you really don't know how long to render. We've caught a lot of problems with ads, third-party content and other things, where we were serving up the page in a normal amount of time, but it wasn't rendering right and it was broken for our users. Now we have insight into that. We can raise the alarm, and try to fix it.

We've had a lot of issues with third-party ads. We were able to get them to clean up their act after we could show them the data that it was broken.

Instead of guessing, we have real data. That's really improved. Instead of saying, "Hey, everybody fire up your browser and see if we can reproduce this issue," we can just look. That's really been helpful.

Things mostly work well. I would think maybe more integration; pull things together more; integrate this analytics with this dashboard, with that analytics; and so on. Just kind of tie everything in one spot.

I have not encountered any stability or scalability issues. I'm not sure how many page views we're doing at this point, but we haven't had any issues with it, and it's a lot. It's a lot of page views. I know it is.

We use technical support from time to time; nothing serious, just some questions; things like that. They've always been really responsive; definitely quick in getting you the answer in a timely manner.

I think they also looked at Dynatrace. I guess I know how that went, because here we are, with AppDynamics.

In general, when I’m selecting a vendor to work with, the most important thing I look for is the ability to get the job done and actually perform.

We also use AppDynamics APM, and we use the database monitoring a little bit. We’re definitely happy with them.

The main thing is that you can use the tool to visually see the transactions happening; figure out the bottlenecks quickly; and the ability to drill down from a high level and go down to the details and figure out where bottlenecks are.

Our architecture is very complicated. We're an e-commerce company, so we have a lot of integrations, a lot of server types, all kinds of server types. What AppDynamics lets you do is see all of it at a high level and then drill down to each node and figure out if we have a real problem.

If you want to complete the picture of monitoring applications, I think AppDynamics should invest more in client-side monitoring. That includes having smart plugins to figure out if you have issues, and JavaScript running, and things like that. For example, companies like Bugsnag complete the picture. If AppDynamics wants to complete their portfolio, I think they should invest in the client side, because client side is growing.

We use Bugsnag as a complementary tool. It has features that I'd like to see implemented in AppDynamics.

The tool is a little complicated. I think the UI should be more friendly. It should have a simple version and a customized version; an advanced mode and simple mode. Simple mode should guide you more, should have more straightforward flows for newcomers. Then, as you move along and become more of an expert with the tool, you should have an advanced mode and change the view to something with more details. Right now, you go in and it's overwhelming.

One of the biggest problems is when you connect it to database monitoring or other nodes, it also has some impact on the system. You have to figure out the right things to monitor; for us, we have to pick our battles.

It can be slow at times. I'm guessing that maybe it's mainly because we have a lot of information that it has to process. Other than that, I think it's fine.

The first thing is you need to identify where the main issue is: do you need end-user monitoring or do you need more of an infrastructure monitoring tool. Then figure out where to place it and how to connect it to everything.

In general, when I’m looking to work with a vendor, the most important criteria are fast response, and having the right attention to details when we have an issue.

We also use AppDynamics Database Monitoring. We tried a few other tools, like the End User Monitoring. We tried a lot of tools. We have been using a lot of AppDyanmics portfolio tools. In general, we're happy with them.

It's real time; you get data back as quick as the tool can process it. It's a very good tool for real time getting to things quick and fixing them.

Our mean time to resolution has been reduced drastically, I think, within the last year. I've only been there like six months, but I've heard since they got this application, that things have really gotten a lot better.

We have hundreds of services and multiple shared health rules for alerting for each of them, AppD has no easy way to pull up all the health rules for a particular service to send off the each app owner to validate alerting thresholds.

AppD can currently extract all the health rules into one XML file but dissecting that into something easy for an app owner to review would be very time intensive.

I think we've had a few blips but it’s been fairly stable.

It has scaled well. We're growing really, really big time this year. It's managing the new inputs.

Set up your processes first and make sure everybody knows what they're doing. I recommend basic training of what it looks like.

I think the big thing is, if you're alerting on something, you want somebody to fix it right away. If you don't have a plan in place there, then everything else is kind of meaningless; for example, if you only see it an hour later.

It's the best thing out there. Something can always be better; nothing's perfect.