Splunk AppDynamics Reviews

The features we find most valuable are real-time monitoring, seeing transactions, being proactive and easy to focus on the real problem.

I remember a case that would have taken maybe four or five days to find the cause. Now, we find it in two or three hours. APM has really made it more efficient. It really helps.

Well, it's not really about APM, but the network monitoring I'm really interested by that.

We're basically starting so we're not yet very good at it. Again, we still have a good support to help us.

We have not had any stability problems.

We have not had any scalability issues.

We have used technical support a few times and we found it to be very good. Response time is good and their tips are good; very helpful.

We did not have any previous solutions.

I wasn’t involved in the initial setup.

We compared AppDynamics with the IBM Tivoli IT. They failed so that's why we went to AppDynamics.

APM probably applied more to us than others perhaps. This is an application monitoring tool so you need to really understand it and implement it properly. The application team needs to know about its features and capabilities to get the most out of it. We're new at this, so it's a new paradigm that we have to bring in our company. Being on the event team, I'm not looking at the application for the app team. Sometimes we're looking at the dashboard and we see something wrong. We feel that they're not really taking action. Sometimes we just call them, "Hey, by the way, can you have a look at it?" So, integration with the actual application team could be an improvement.

I think a vendor should be available, have deep product knowledge, and be helpful.

The most valuable feature is giving end-to-end, about the business transactions, specifically, which is an area everybody struggles with. What they are looking for, basically, is how customers are viewing the transaction, from the end-user perspective, which is useful for the business people. They can streamline where they want improvement, but it also gives you the details down to the nitty-gritty that the developer teams are responsible for. Along the way, it's also showing you the overall performance for the infrastructure that you have for the application.

A benefit is ease of use, compared to other products that we have seen before, such as Wily. You get to the information a lot quicker, instead of spending an hour trying to get to the point that you're looking for, especially with the workflow maps that they have. It's really very easy and intuitive also. Looking at snapshots, you can quickly pinpoint where you want to look at.

Specific to what our experience is, because we're using Cloud Foundry, we're using an extension to monitor the infrastructure for that; that's probably the weakest point for it, because it basically collects JMX metrics. One of the things that we see missing when compared to Wily Introscope is the concept of calculators. You get a group of metrics and you make calculations based on it. That's something I've seen people require. It's something they want to see on their dashboard. They have the metric browser; it's not capable of doing such a thing. That's one thing that people would like to see.

Dashboards, at least the basic ones that we have, because we are not licensed for Analytics, as of yet; it seems basic and not the best area of the product. The dashboards could use some improvement.

So far, it is pretty stable; no downtime. Our implementation is high availability also, so it's a clustered environment. So far, we haven’t had any issues that I am aware of.

So far, we haven’t had any no scalability problems; we size it properly, as far as hardware. Maybe we even oversize it sometimes. So far, we haven’t had any issues.

So far, personally, I opened three tickets so far and I got what I wanted to get. I was pleased with the resolution.

The only complication with initial setup was the PCF, the Cloud Foundry monitoring. I guess it wasn’t something AppDynamics had planned for before. I don't know. It's a new area to everybody. They rolled it out because it's microservices; there were a lot of teams involved, just to get the tiers and nodes in check. That took a lot of work. Also, we have multiple data centers that are sharing the same application, so we needed to take steps to distinguish the data centers from each other as well.

Take the training; take the time to learn it; explore it. That's my advice.

We use AppDynamics Server Monitoring to keep track of live errors, loads, calls per minute, etc.

We can view the server activities, including issues in the process, with a single click. In the case of a script, we can create one branch to learn about function failure and the reasons behind it.

The product's initial setup process needs improvement.

We have been using AppDynamics Server Monitoring for six months.

It is a stable platform.

We have 150 AppDynamics Server Monitoring users.

Every organization has different requirements to set up servers. The configuration is tricky and requires a lot of tools. In such cases, getting assistance from the product's support team is easy.

The initial setup is complicated.

I rate AppDynamics Server Monitoring a seven out of ten. Its setup process is tricky. It is very different for every server. I recommend using Microsoft, Linux, and VMware as they have their monitoring tools.

I primarily use AppDynamics for application performance monitoring.

AppDynamics provides visibility on slowness or problems in production and processes in revenue-related products or software, as well as generating performance and availability metrics. This enables understanding of users' end-to-end experience and provides information on user behavior.

AppDynamics' most valuable feature is Business iQ, which is based on analytics.

The Log Analytics feature is a bit complicated. There are also some bugs in the solution that need to be fixed.

I've been using AppDynamics for five to six years.

AppDynamics is stable and reliable.

AppDynamics's technical support is great.

Previously, I used Micro Focus OpsBridge but switched as it wasn't keeping up with the latest market trends in monitoring.

The initial setup for the SaaS solution requires little to no effort, but the on-prem version is more complex

AppDynamics is one of the most expensive solutions on the market. The typical licensing fee for a small customer would be $500k plus, with additional fees for professional services. The price also varies depending on whether the customer goes for the on-prem or SaaS solution, with the on-prem version potentially extremely expensive because of the hardware requirements.

We evaluated Moogsoft and Dynatrace.

I would rate AppDynamics nine out of ten.

We've been able to chase down some big problems with our website. When the problems are more obscure in nature, it's allowed us to drill down into our code and find things we wouldn't normally be able to find as easily.

It's actually saved us tons of man hours because we've been able to narrow in on where actual problems are, rather than having to chase our tails looking at everything along the way. It's changed the target area. It's reduced that dramatically, so we know where to look for problems quicker.

Things I struggled with most were the visual widgets in dashboards. I feel like there could have been more online guidance.

Synthetics would be much easier if we didn’t have to learn Python and could use a GUI tool like Dynatrace.

I would also like to see alerting if our transactions or log transactions daily allowance has been met.

I like the looks of the network feature coming. That looks really cool. As far as the product itself, I've been really happy. Everything I've needed from it has been easy to find. Beyond the items I’ve mentioned, I don't have any big ideas for enhancements. As I’ve mentioned, I've been happy with what we have.

It's worked when we needed it, all the time. It's been very stable. I've never had an issue with it.

I don't have much experience with scalability. We're smallish, I'd say. We're a web farm of 4-8 servers. Even during the busy times, it's scaled for what we've needed it. I've never had to test that.

Technical support has been awesome. I've only had to call them a couple of times. Every time I did, I got an immediate response and they weren't happy until I was happy. Of all the tech companies I've ever worked with, they're definitely one of my favorites to work with.

We did not previously use a different solution. That was the thing: It was an untapped area for us, really. I guess when we found them at another conference, Velocity, a few years ago, and decided it was something we really needed.

I think my boss at the time looked at New Relic and maybe Dynatrace. We didn't know much about APM at the time, but I think pricing was the overall factor there.
To be perfectly honest, to me, the most important criteria when selecting AppDynamics was the experience. We had a really great sales team to work with. They made it easy. The support we got along the way was phenomenal.

Take time to get into the forums. That wasn't something we did right away. The forums, the online AppDynamics University, all of them are really, really helpful.
I've been really happy with it and everything we want it to do, it's done. If it was something we thought couldn't be done when we reached out to support, we got help to the ends we needed it.

We will be using other AppDynamics products. We just started, actually; we signed a contract a few months ago. A lot of that stuff is new to us. We're mainly skilled in APM. We're learning the synthetics and the transaction analytics now, which look to be really promising. I'm excited about the demos we've seen. We've had some professional time with a couple of consultants, who showed us how to use them. It looks really, really valuable.

The most valuable feature is the view it gives me about the wait states in the database. It shows me the snapshots for the database queries; some of the details behind what might be contending on the database if there's an issue. I think that's really insightful for the applications that we use. That's pretty helpful and beneficial for troubleshooting.

The biggest benefit we have found is that we are quickly able to identify the root cause, especially if it's in the database layer. We also use AppDynamics on the app layer as well. It quickly helps us get to the root cause. That's been the number one benefit of using it.

I definitely want to see some drill down capabilities, especially at the database layer, because the snapshot gives me up to a certain point where I can see the wait states. I can't really see at that particular point in time, a certain SQL was causing the issue in a real time basis, and I can alert someone on that basis. I definitely want to see some drill down capabilities at that layer.

I've seen some demos of the upcoming capabilities such as doing monitoring at the network layer. And then the EUM, the end user monitoring; I definitely will be looking forward to using those in the future.

I haven’t given it a perfect rating due to the future capabilities, which are definitely coming.

So far, we have not found any instability caused by AppDynamics APM. We have had instances where, just to eliminate possible causes of issues, we have turned off AppDynamics, but it has never caused us issues with the database being either slow or going down.

We haven't really had the need to scale it. We're in the early part of the journey in our AppDynamics deployment, but we will soon be going there. We still have to get to that point.

We have used technical support a couple of times. When we had the new release, the deployments were not as smooth as we thought. I think we had to engage the AppDynamics engineer, and a couple of times for the configuration that we just did not know. It was probably a training issue more than anything else. Other than that, it's been self-sufficient as far as we can tell.

Tech support were really helpful. We have a good partnership with AppDynamics. That's what we appreciate because they understand how my company works, the culture, the scope and the ecosystem. We really like it, having that partnership.

We run a lot of third-party packages, and we fly blind to what happens inside. We have tons and tons of logs. To go through those whenever we have an issue takes days or weeks. It's a similar story, I think, across the board. For us, though, the applications being so critical, we need to get to a root cause and fix it. Until that point, before we had AppDynamics, it was a constant back and forth with the software vendors. With this tool, since we’ve had it and have been able to pinpoint where the issue is, we can get on to the root cause really quickly.

The initial setup was kind of different and new. I wouldn't describe it as complex. Once we had the person from AppDynamics sitting next to us, we could quickly get to it.

There weren’t really any other companies we looked at before we chose AppDynamics. In our company, we have another tool that they use. I think AppDynamics is quickly picking it up. But we as a group never looked at any other tool.

In general, when I look at working with a vendor, the capabilities in the product is definitely the most important criteria. That's number one. The second thing is, as I’ve mentioned, if you have a good partnership and a good representative from the vendor side who can represent your issues to the product teams and get those features in. I think that's kind of critical for us.

If colleagues looking to implement database monitoring asked me for advice, I would definitely advise them to look at this APM tool, first of all. Then, basically just work with the engineers initially and get self-sufficient with the tool. And spend some time with the tool. If it's a training issue, get some training on the tool itself.

As long as they know their space, they know their infrastructure, they know their database ecosystem, it should be pretty easy.

We use the AppDynamics database monitoring plus the APM on the app side right now.

Right now, we use a lot of the metric browsers, we use the APIs to then ingest that into Splunk, and then create nice visual graphs that upper management can then digest very easily. We use AppDynamics not only from a troubleshooting point of view, but also for trending, analysis, and capacity.

It's definitely cut down our troubleshooting, from a mean time to restore or repair, and pinpoint the actual problem that we are having; reducing that time.

I don't think we've tapped into everything that AppDynamics can do. I can't really mention something it should do because AppDynamics might already do that and we just haven't implemented that yet.

Nonetheless, I know that a lot of the problems that the people are having is they lost work. It'll be really good if they could retain the data a little bit better.

From my standpoint, it’s pretty stable. I know that when we first set it up, we put everything under one application. Now, we are kind of breaking away from that, and we are losing a bunch of the data. From that standpoint, people are getting upset, but I understand that's the limitation of the app. I think some people just need to move on.
Once we get everything the way we want it, the maps are going to show up the way we want it. I think it will be a lot more beneficial.

Scalability is a lot better now that we can see one application, can see the other application, whereas before, we didn't have that visibility. That's why we put everything under one application. Now, I think we can do as much or as little as we want.

I personally haven't used technical support but the company definitely has. They're on site all the time. I know from talking to our monitoring guys, they love it. They think that the support is always there and always readily available. They are the administrators; I am more of a power user.

We weren't previously using any APM solution. We were flying blind. We knew we had to do something. That's when the monitoring manager got wind of AppDynamics and really pushed hard for us to implement it.

I was involved in the initial setup a little bit but not all too much; just from a 40,000-foot view of, “Hey, this is what's coming down. You might want to play around with it.” I wasn't involved in the installation or anything of that nature.

From what the installation people said, initial setup was pretty easy. All you had to do was put the agent on. I know our development were kind of balking about putting the RUM JavaScript out on all their pieces of code. Now that it’s out there, they're pretty good about adding more and more to it because they are seeing the benefits of doing that. From a standpoint of installation, I think everything has been running pretty smoothly.

I don’t know any of the other vendors that were on the shortlist. I am sure there was but I don't know. I wasn't a part of that conversation.

If you're not getting the support or if you're not getting the answers when they are trying to troubleshoot, then this is a definitely a really good solution and it will save you time in the long run.

With the benefits of pinpointing the issue quickly, we can get either our servers or our application up and running better. We've pinpointed a lot of long transaction times and were able to fix that. Not knowing that, because we fixed that, it also fixed three or four different applications.

It’s also nice to see the mapping. Once you start building all these things and its building on top of each other, AppDynamics does a very good job of showing, “Holy cow, we actually are talking to all these other different servers.”

As I’ve mentioned, we were flying blind and now we are starting to see. It's been a lot better.

In addition to AppDynamics APM, we use EUM as well. We are trying to get our company off of Google Analytics and go straight AppDynamics, but it’s a slow boat.

The easiest thing to do is to find all the transactions that you don't necessarily know about, what they are to discovery. A lot of times it shows you things that you had no idea was going on like performance problems you didn't know existed. It ties everything together and makes it easier to relate one transaction to all the different bits and pieces.

For example, one of our guys found that another system was hitting his system every hour, which was causing a lot more traffic than it should have. It wasn't affecting any other parts of the system and wasn't impacting the users, but was just causing way too much undue load on the system. They were able to track down why it was doing that and get the problem resolved in a week.

APM gives us easier troubleshooting and notification of issues. We can report off of that data to show application performance improvements over time. For example, we know that in this release, our baselines were X, Y, Z. The next release, we can then say, this was 20 percent faster or this was 10 percent slower. And then be able to figure out what we need to take off or what's just humming along fine.

We also use AppDynamics Infrastructure monitoring and End-User Monitoring.

Increasing the 200 business transaction limit would be great. The ability to compare releases a little bit more and with a little bit more accuracy. Right now, it'll show you the previous release and the next release. And it shows you all the numbers, but it doesn't you any relative change between them. You have to do all that on your own.

Overall, stability is very good. We've never had much of an issue with any of the agents. They install quickly and install easily. We have had a couple of glitches in the UI, but support's been very, very on the ball, both responding and handling issues.

Scalability seems to be going pretty okay. The 200 business transaction limit, while I entirely understanding the reasoning behind it, it's just irritating. There's a lot of times I want to monitor more than it will allow and I have to make sacrifices in some things for performance.

I look for responsiveness in a vendor. Whether they're willing to work around our schedule, our needs. Just having knowledgeable people on the front line is great. I mean, just all the initial support. Level one helped us and they've been able to answer most of my questions right off the bat. And they generally seeming to care about the product and care about their clients.

We didn't have anything at all. So, it was obvious that we needed something and AppDynamics was just really easy to get going and gave us more than enough information.

Initial setup was fairly straightforward, just to get it up and running. It takes an hour to do the install and the initial configuration. But once you're able to see everything that it can give you, that's when the complexity really comes in. You don't know what issues it will find until it finds them. From that, you can then branch out and build on different types of monitoring. But just getting it going, you run the installer and pick what you want and done.

I wasn't involved with choosing a solution, so I don't know.

Do it right from the beginning. Do a lot of planning. Everything flows from getting it setup correctly originally. And in a lot of ways, if you go and change something, if you need to kind of go back and re-do some things, you're going lose all your data historically. So do it right from the beginning.

I give APM an 8/10 because nothing's perfect. There are times where we had a couple of outages over the past couple of weeks. Just an hour or two where it was not available. We had to increase memory twice on the database monitoring agent. And when that dies, it doesn't respond. It doesn't report and it doesn't notify. So we go in a week later, look at our database information, and just don't have a week's worth of data. And that's an artifact of Java taking way too much memory. It's just little things. Nothing major.