Splunk AppDynamics Reviews

I think the most important thing is the end-to-end view that you get of all of your servers when you set it up. You can see where problems are without having to actually experience them or tell they're experiencing the problems. You can be preemptive.

I think it allows you to go down and get real data about what's wrong, instead of having to email around screenshots. It let's you actually get the depth that you need, even the code level and code lines and that kind of thing.

I think a little more control over which transactions get that depth attached to them would be good. Right now, it seems like there's certain thresholds that you can set, but it would be nice if there was a more dynamic way to archive transactions, or keep around certain transaction types.

Stability and scalability look pretty good, from what I can tell; especially the cloud SaaS APM solution.

We have not needed technical support.

I was not involved in the initial setup.

We are currently moving from a monolithic application to a more service-oriented model where we're going to do micro-services. Spring Boot was the choice for that, because it has actuator support which provides some of the same features. We're looking at that, and weighing this because we already have it. We want to see if we can use of both, or maybe just use AppDynamics going forward.

I think price and scalability are important when choosing an APM vendor. If it's a third party solution, is it going to be able to keep up with the solution you're using? How is the technical support, and how cutting edge is the solution. Are they keeping up with their competitors? So far, we have found all these things in AppDynamics.

From a reporting and dashboarding perspective, their API, which is what I deal with the most, is unmatched by any company that I've come across.

We're able to get a single view into applications and their performance; the way they run, errors, and trends. We're able to turn that around back to the developers and help them tweak their code and applications.

Coordinating upgrades across systems would absolutely be a huge benefit. I don't deal with a lot of the upgrades. I just get the emails saying that there have been upgrades. We're on the SaaS platform, so I don't see the platform upgrades, either. Nonetheless, that would actually be a huge benefit.

I haven't seen any downtime myself.

I haven't seen a whole lot of limitations from an input perspective. It’s been pretty good so far. The performance actually blows the competition away, from what I've seen.

When I open a ticket, it is resolved quickly. They are very responsive; very fast to get back to us and very thorough with their answers. I’m happy with the resolution.

I was involved in the setup of the single sign-on integration for our company, as well as getting the users set up and trying to get permissions set up. That required a little finessing and conversations with AppDynamics, but for the most part, it was pretty simple.

Reach out anytime you have questions, because they're very responsive to answer.

My favorite part of the application is that it auto-baselines the application that you instrument with it. I work with other monitoring tools such as SCOM and Splunk. These tools are great, but the automatic baselining offered by AppDynamics is like an easy button.

Products like SCOM and Splunk require you to have to know exactly what you want to alert on. From a Splunk perspective, that is generally a very specific log entry such as an error. SCOM deals with hard thresholds and there is work to tune those to be meaningful for an organization. What make sense for organization A might be completely different for organization B. For example, when to alert on a drive filling up. Does 80% make sense and give enough proactive warning to get the issue resolved?

With AppDynamics, the product keeps track of how your application is performing and rolls that into an aggregated value that is compared against how the application is performing right now. It then lets you alert on a deviation away from what is considered normal. This creates immediate value in the alerts it provides without any real interaction from a tuning standpoint.

With its automatic flow maps, as well as its ability to automatically baseline key metrics out of the box, it allows support individuals to quickly focus in on the exact location of the application problem reducing MTTR. It also has enabled us to be more devops focused, creating stable releases in a faster, more efficient manner.

As an administrator, I would love to be able to manage the update of agents from the controller itself. This would allow for enhanced version control, as well as eliminate the need to target various applications and their corresponding servers individually due to their unique configurations.

I would also like to see better license management from an auditing standpoint. Knowing how many licenses are being consumed by an application would be a great feature. Being a large organization, it would assist with understanding total cost of ownership, as well as growth predictions on a per-application basis.

We have been using the product for the last three years for numerous applications.

While I wouldn’t consider this an issue, when the business originally brought AppDynamics in, a centralized support structure had not been identified. We ended up with a controller for each application, which is not the ideal enterprise solution. When I took on support of the product with my team, we consolidated to an on-premise enterprise controller. That process was extremely easy to perform so, for us, it was really more of a bad design problem that my team had to fix.

Technical support and customer service have been amazing. I have been able to get support both through the portal, and from our sales support extremely fast. They have a great customer service focus. This is one of the reasons that deployment of the product is also so easy.

AppDynamics setup is very easy from an installation process. The best part is, when you decide to go with the product, they work directly with you to assist in the initial implementation to ensure you get the most of the product.

AppDynamics helped with the initial implementation. That was very focused with the support teams of the applications. I would absolutely recommend getting your development teams involved ASAP, so they begin to use the tool and see its immediate value to them.

We also evaluated New Relic. In the end, the features, ease of use, and customer service provided by AppDynamics was what tipped the scale towards them.

They offer a free trial. If you are struggling with finding the root cause of a reoccurring issue, then give it a shot. We got immediate, actionable results.

My rating reflects its ease of use as well as the scope of solutions that it can monitor, including MongoDB.

It is a good monitoring tool. Its stability is very good.

Their support should be improved. Clusters and monitoring can also be improved.

I have been using this solution for around three years.

It is very good.

Its scalability is fine. It is not bad, and it is 60% to 70%. Sometimes, the containerization service and scalability take time.

We have seen an ROI.

If you are managing more than 1,000 servers, it is good to purchase the AppDynamics tool. From the monitoring perspective, it is a very good tool.

I would rate it a seven out of 10.

We primarily use the solution for database monitoring. We also have defense solutions available to monitor the database performance. We use AppDynamics in our pipeline.

The feature that is most valuable to us is the snapshot feature. It allows us to get a snapshot of different SQL scripts that are being executed simultaneously and we can identify everything we need on them.

The solution offers good monitoring.

I'm only working as an administrator on the solution, so I'm not in a position to really discuss too many technical aspects of it. 

The application monitoring needs improvement. It needs to be easier for someone who isn't a proficient developer. 

For example, if we use Java for monitoring events to gather history-based data in regards to the application, it should provide a better core-controller. When we monitor any Java application, the approach for us is to identify a set of classes as part of Java programming. These particular classes needs to be executed so any end-user using AppDynamics would be able to see the culprit class. There shouldn't be a need for a final report. Yet, we don't have a feature like that at this time. A person who is monitoring everything needs to have very good knowledge about the solution and not everyone is a proficient programmer.

I've been using the solution for two years.

I haven't personally faced any issues with scaling. However, we have a limited number of licenses available. We've been allocated four licenses to monitor four different items. Therefore, I don't have the availability to scale currently.

The initial setup is pretty straightforward. The initial implementation is quite simple. It takes about one day to fully set everything up. However, sometimes we have compatibility issues. For example, AppDynamics is compatible with the C language.

Our sales team initiates the AppDynamics license and then an internal team handles the events around implementation. We have a good team available from Citrix as well.

The solution we are using is SaaS-based. The controller is deployed on the cloud, and we have integrated different Linux environments with it. There are a couple of Java agents as well as machine engines and a DB agent that we utilize.

I don't have too much interaction with the teams that handle the solution, so I don't know if I have any advice to give other companies in relation to implementation. I don't have too much exposure when it comes to database monitoring and am not overly familiar with the application itself.

I'd rate it at least a six out of ten based on my experience with the solution so far. I only use limited features for Oracle database monitoring. 

We have a complex application. We do payments which are highly transactional in nature. With different kinds of workloads that you see in the production environment, how do you really track down specific issues which your lab testing environment can't really reproduce? Your production environment gives you certain workloads, which basically enable you to look at your application more closely. No lab test could really simulate that sort of a load. APM really helps us in getting down to the bottom of these sorts of workloads; how code responds to these sorts of workloads and how we can make our application deliver better latency and a better end-user experience.

Given an extremely transactional, highly complex workload, you just cannot use your testing lab to stress all of your code parts. First of all, it has made us very agile. What happens is, now, you can actually take any one of your deployments or releases, roll it out into production into a very limited set of servers, look at how the APM works, and it gives you insights onto the how the code that you just pushed out is performing.

If everything is fine over a period of a few minutes or a few hours, you can actually roll your deployment out very quickly. You don't have to have an extremely complicated test harness in your preproduction environment. You don't have to go through extensive testing cycles before releasing something into production. It really makes us agile in terms of releasing to market quicker.

For me, the single largest area with room for improvement that I've been requesting the AppDynamics team to deliver for us is APM support for Ruby on Rails and for HHPM. These are the two language environments that we use quite heavily in production. That's something that I'd like to see support for.

Stability depends on the configuration. We work very closely with our solution architects, with AppDynamics, because there's always this question in the minds of consumers: A tool which can do so much as AppDynamics, how do you ensure that it runs with minimal overhead? You've really got to work with the AppDynamics team to size out your environments; that makes it stable for you. That's been our experience.

I can't comment on scalability because our infra is fairly small. We have a total of around 150 nodes that we could probably end up instrumenting. Right now, we do far less than that, so I can't really comment.

Technical support has been pretty good. In our case, we use a few programming languages which are still not supported by AppDynamics, so we've reached out to them to help us with road map information. They've been pretty transparent about when support could get rolled out to these sorts of languages that we use.

For the more run-of-the-mill sort of tickets, where we have issues with the configuration or using the product, it's been pretty good. We've liked our experience with the tech support team.

We had been using a mix of proprietary tools that we developed in house, along with third-party solutions. We were able to get the job done, no doubt about that, but the problem is never having an integrated view of how your application performs. We have uptime alerting running differently; we have business KPI monitoring being done differently; and we have end-user behavior being tracked differently. It was very hard to find a correlated view across all of these four. To debug specific sessions or to debug specific instances, I think that's where AppDynamics really comes in. The integrated view that it gives of your application.

I was not directly involved in the initial setup but my team was. It's pretty straightforward. I think it's really important that whoever is setting up the application first fundamentally understands what the application does. I think that's critical. The tool is fairly complex and powerful. The setup needs to be handled by someone who, on this side, really knows what the application being monitored can do. If you put a rookie on the job, it's going to be really tough.

We did consider other vendors. We were looking at New Relic. As a developer and as someone who builds and has a team who builds stuff, I feel New Relic is actually a very powerful option. However, as I mentioned, we wanted something that could work on-premise.

We went with AppDynamics because we are in the payments industry and from a compliance perspective, we needed an on-premise solution and AppDynamics was, I think, the best solution that also worked on-premise.

In general, the most important criteria when selecting a vendor like AppDynamics for us is, first of all, from the product perspective. As I mentioned, we had a mix of various proprietary and third-party solutions that we were using earlier. We needed a product that could provide end-to-end visibility into the infrastructure and the application. That was a high priority for us. Beyond that, what we really needed was a global presence with enough strong local support. That was something that AppDynamics brought to the table.

Make use of all of the training material and the university. There's some really useful information in there. Also, the two other things that I’ve mentioned elsewhere:

• Ensure the person who is deploying AppDynamics in your environment is among the top-most performers of your team, someone who knows your application in and out.
• Combine that with good, strong consultation by the AppDynamics team. Get these two in place and you've got a winner on your hands.

The reason why I have not rated it higher is the lack of support for HHPM and Ruby; bring them both and I would rate it higher.

We have analyzed so many of our APIs and web services. It showed how much data and how many times each and every API and web service is used. We didn’t know how much they cost; we are paying thousands of dollars for our web services. If we can save on those costs and enhance the performance, that's priceless.

I think the performance and interface are the most important features.

The way we execute it, it takes a bit of time, like every tool. If they can improve that; instead of taking 10 seconds, say it takes 5 seconds or 3 seconds, that would be great. Maybe some more CPU power or something like that could be an area to improve.

It's pretty stable; there has been no down time, and it does not hang.

It scales very well for our needs.

The support is awesome, so whenever we get something, we call them. We get 24-hour support, which is great.

Initial setup was straightforward; that's awesome.

We looked at many other products at a few conferences. We saw a couple of more products and then we came back to AppDynamics; we are working with them for the last two years.

We decided to go with AppDynamics based first of all on performance, features, and the benefits we would get; whether the product was being offered per instance, per developer or for the whole team. The price, is it per instance or per year? We decided, based on all of these, that we should go for AppDynamics.

Go through the features it has; it has many of them. If you just buy it and use it for small things, it's not worth it. It has many features and capabilities; it is capable of doing many things. Go through the features in detail, or even go through training to get an idea of what it can do. It's a big product.

Line-level tracing: This helped massively with identifying and eliminating performance bottlenecks. We had a significant slowdown in our app that we were struggling to identify. Using AppDynamics to trace hosted code to bottlenecks proved invaluable. This however only got us so far. When we reached the limit with AppDynamics, we sought advice from their technical team. After all, we were using a very expensive product that didn’t get us all the way. Under NDA, AppDynamics took a working branch of our code and investigated the bottleneck internally. They did this using other tools besides AppDynamics. This was beneficial to them to identify things that could not be achieved with AppDynamics. Later, they were able to discover a way to make this easier within AppDynamics.

AppDynamics has become the go-to tool for issue identification. The DevOps team was able to take more ownership for defect detection to improve discovery time and reduce risk of issues becoming known to end users. It also reduced the involvement of third-line support in issue detection.

The UI is clumsy and slow. The AppDynamics portal had an Adobe Flash UI, a bit dated for a modern SaaS. It had an old feel to it; unusual for a company with advanced technology. It would often take a while for the portal (controller) to load, making it a little tedious to use at times. I’m not sure why it took so long, maybe it was doing real-time processing of data, which, if so, I’m more forgiving.

I used it for three years.

I did not encounter any stability issues.

I did not encounter any scalability issues.

Techccial support is 10/10. See a case study from my previous company here: https://www.appdynamics.com/case-study/the-test-factory/.

We previously used New Relic. We switched because AppDynamics offered a broader and deeper range of functionality.

Initial setup was straightforward for Azure virtual machines, but not so easy for cloud services. The installable was difficult to get running in cloud services, but the AppDynamics technical team were supportive.

AppDynamics is a premium tool. You’ll soon realise this expense would’ve been greater without AppDynamics.

Before choosing this product, I personally did not evaluate other options.