Splunk AppDynamics Reviews

When compared to its major competitor, Dynatrace, AppDynamics stands out by providing dynamic learning capabilities for infrastructure and server metrics. Unlike Dynatrace, AppDynamics enables dynamic baselining for all server metrics, such as CPU and memory. This allows customers to establish patterns, like CPU trends every Wednesday from 9 to 11 AM, and set dynamic baselines accordingly. With this feature, alerts can be triggered based on deviations from the dynamic baseline rules. This capability is distinctive, as other APM solutions and monitoring tools lack dynamic baselining options for infrastructure visibility.    

If we consider the implementation of alternative solutions, such as Dynatrace, there is a notable difference in the approach to agent-based service monitoring. For instance, Dynatrace employs a single-agent solution, which can pose security concerns. When installing Dynatrace, granting the agent ld pro payload rights is a requirement. In contrast, our solution ensures a more secure approach by not requiring root and administration access. While we currently utilize an agent-based solution, there may be a shift in the next one or two years, possibly with the adoption of Open Telemetry. It's anticipated that many APM vendors, including Dynatrace, may alter their structure or strategy for implementation. However, as of now, the trend is towards an increasing number of implementations daily.

I have been using AppDynamics Server Monitoring recently.

It is very stable and I would rate it 9 out of 10. 

It is very scalable and I would rate it 10 out of 10.

It's very easy.It takes couple of minutes only.

It's true; it's not an inexpensive solution. Dynatrace and AppDynamics are consistently on the pricier side. However, when comparing with other solutions like Datadog or New Relic, it becomes apparent that they are significantly more affordable. The pricing may seem high at the list or discounted level, but what truly matters is the business value assessment. After completing this assessment, customers often recognize the value proposition and find the cost justified.

In all honesty, APM solutions, including AppDynamics, tend to be expensive, and they may have fewer features compared to other legacy monitoring solutions. I typically advise against using AppDynamics or similar APM solutions solely for server monitoring due to their cost and potential limitations. To maximize usefulness, it's crucial to complement these solutions with other monitoring tools and features.

I would rate it 9 out of 10.

The solution is used for observability, AIOps, monitoring microservices, SAP monitoring, and application performance monitoring.

AppDynamics is predominantly marketed and sold as an APM solution. Customers use it for both database and application monitoring. I have not seen a customer buying AppDynamics only for database monitoring. The product is good at database monitoring, availability and performance monitoring. I have always used it as a holistic product.

The product requires high maintenance. We need a dedicated resource to manage it because the solution manages a complex environment.

I’ve been using the solution as a system integrator for eight years.

The tool is stable, but our clients are not using its features to the fullest due to a lack of knowledge of APM. The customers are not very clear on what features an APM product offers. Customers have a limited understanding of APM and its use cases.

The tool’s scalability is good. Our customers are enterprise-level businesses such as large hospitals, manufacturers, and banks.

Technical support is good. Support must provide faster responses for production-related issues.

Positive

We have used ManageEngine before. AppDynamics is better than the other products we have used. The tool provides a pretty good user experience. The dashboards are very well-defined. Business-related data is very well projected on the dashboards. The technical team also gets good information on their dashboards.

AppDynamics monitors pretty much all the applications, though the applications are built on various technologies. ManageEngine has a limitation. It cannot monitor various technologies. The most important factor is security. Security is very well defined in AppDynamics, whereas ManageEngine's security is not up to the mark.

The initial setup is neither easy nor very difficult. It requires specific knowledge of the infrastructure. When installing the product, we must be aware of how it will be configured at the database, application, and infrastructure levels. Earlier, the tool was deployed on-premises. Nowadays, customers are willing to deploy it on the cloud.

Typically, to install the product, we take help from infrastructure experts. We need to be aware of the infrastructure before installing the product. The deployment takes seven to ten days. We need one architect and two engineers to deploy the product. The number of resources required to maintain the solution depends on the environment. We need two resources for medium-sized environments, but we may need four to five resources for larger environments.

One of the main downsides to the solution is its cost. We pay a yearly licensing fee for the product. AppDynamics and Dynatrace have almost the same pricing. Compared to ManageEngine, AppDynamics is relatively higher in cost. For cloud-based solutions, users only pay for licenses if they opt for a subscription. However, for on-premises solutions, they must buy support separately.

The application layer in AppDynamics performs fairly well. However, network monitoring is not at an advanced level. It is mediocre.

People wanting to use the solution must not use it only for database monitoring. It should be used for end-to-end application performance monitoring. If someone has requirements involving applications, observability, and AIOps, they must consider the product. If they need only database monitoring, several other tools are available in the market that are lower in cost and offer a lot of capabilities.

When it comes to end-to-end monitoring, network monitoring also plays a crucial role. It is an area of improvement for AppDynamics. Network monitoring could be better. AppDynamics has acquired a product called ThousandEyes. How well the product grows in the network monitoring space is yet to be seen.

Overall, I rate the solution an eight out of ten.

System monitoring and real user monitoring were the two domains in which the product was used in my company.

AppDynamics Mobile Real-User Monitoring was a tool directly used by my company's client. I have no answer if you ask me why my company's client decided to use the tool. My company's client used the tool to monitor servers in their entire business process, including some servers, databases, clusters, mobile users, and for different services.

The most valuable feature of the solution is its GUI. With the product's GUI, one doesn't have to check for details since one can see the entire business flow in one go. At a glance, you can understand where your business flow breaks since the tool's entire GUI is pretty good. Apart from that, the auto-remediation in the tool helps if the CPU or server is getting exhausted by indicating the files that should be deleted. Auto-remediation and GUI are two good features of the product.

Though I haven't explored AppDynamics Mobile Real-User Monitoring a lot, considering the way the setup of the product, I did not understand certain concepts. The way the agentless monitoring and agent monitoring get used is to be decided by the user, but there is no clarification on the setup phase or on how and why to use the aforementioned options. When it comes to complex environments, the best thing you would like is that the setup should be fairly easy. The product's setup phase is a bit tricky and needs improvement, especially depending on the server environment since the product has a specific file format and a specific configuration form.

I have been using AppDynamics Mobile Real-User Monitoring for six months. I am just an end-user of the solution.

It is a stable solution.

Adding users directly to the solution was okay, and I did not face any issues with it.

For one of my projects, less than 150 employees in the company were using AppDynamics Mobile Real-User Monitoring.

The solution's technical support was good. I rate the technical support a nine out of ten. I assume the solution's technical support was expensive. In my company, we were recommended not to reach out to support teams in a very quick or frequent manner.

Positive

The product's setup phase is a bit tricky.

The solution is deployed on-premises.

I believe there was probably an extra charge whenever I wanted to contact the support team.

I would say that if you have a good budget and want a good and interactive tool where you don't have to do a lot of integrations, then you can go ahead with AppDynamics Mobile Real-User Monitoring. If you are tight on budget, considering before buying it is important since the number of users who can use it depends on the licenses. It takes quite a lot to exchange the license and all regarding the tool.

I like the product's GUI since you don't have to put in much effort to see where exactly my process is broken, and you can easily see how many users are using it in real time. The product allows you to check the way it works. Providing alerts to users is really fast in the product, and you have multiple options to receive alerts, like email, mobile messages, or automated voice calls. I can't give the product a ten out of ten rating because if you are stuck somewhere, then getting support to assist you with configuration or with other situations can be a little tricky.

Overall, I rate the solution a nine out of ten.

AppDynamics is primarily used in our enterprise system management for application monitoring. We extensively use it to monitor end-user experience, including mobile applications. We want to ensure that our users have a seamless experience on our website and mobile app. We use AppDynamics to monitor all applications end to end, and it has been a valuable tool in our environment for identifying and resolving issues quickly.

The best features of AppDynamics would be the code application monitoring capabilities. There are no limitations to any specific application, and their support extends to all levels, including mainframe and custom applications. AppDynamics can also be used as a SaaS model, which is a key advantage.

One area for improvement is the MST model. It would be more helpful if it could be offered as a managed service provider model with more multi-tenancy and features.

The focus is still limited to application monitoring. However, in the next release, I want to see if it could be integrated with any other infrastructure monitoring tool or provide better deliverables in terms of absorbency layers; that would be a great option. I'm not sure how AppDynamics delivers that, and it's an approval delay. That use case will integrate with any monitoring tool to provide the absorbent layer; that is the better option, which I look forward to.

I have been using this solution for seven years.

I would rate stability a nine out of ten.

I would rate scalability an eight out of ten.

We used Dynatrace, which is also a performance monitoring solution. Dynatrace is similar to AppDynamics in terms of its capabilities. But Dynatrace is an expensive affair as compared to AppDynamics.

The initial setup is not complex. I would rate it a nine out of ten. The deployment depends on the use case. For example, taking one application will take hardly a week to cover the end to end.

The pricing of AppDynamics is a nine, with one being low and ten being high. It is high.

I would recommend using AppDynamics integrated with an infrastructure monitoring tool, and it will provide a better benefit.

Overall, I would rate AppDynamics a nine out of ten. From an overall product standpoint, AppDynamics has better sustainability in the market with continued support. They also have a roadmap for upcoming releases that aligns with all the monthly activities.

We're using AppDynamics Server Monitoring for the IT infrastructure and server of the customers.

What I like most about AppDynamics Server Monitoring is that it's easy to manipulate and easy to implement. All solutions have the same features, but what sets AppDynamics Server Monitoring apart is that it's really quick to implement.

AppDynamics Server Monitoring has a great interface. As a developer, it doesn't matter whether it's SolarWinds, Dynatrace, or any APM you're using, but it would matter to the customer. A product must be easy to manipulate or use, for example, AppDynamics Server Monitoring, for the customer, but for developers like my team, there's no pressure, even if a solution requires coding.

AppDynamics Server Monitoring has room for improvement in terms of pricing. If the price could be cheaper, it would be great for both the customer and the integrator.

What I'd like to see in the next release of AppDynamics Server Monitoring is a better dashboard for the customer. The dashboard should be more interactive.

I've been using AppDynamics Server Monitoring for three years now.

AppDynamics Server Monitoring is a stable solution. Its stability is good.

AppDynamics Server Monitoring can be scaled up and down according to your needs, so it's a scalable solution.

I find the technical support for AppDynamics Server Monitoring interactive and quick. You can get support WebEx sessions, and if I would rate support from one to five, I'd give a five.

My company works with a lot of solutions as it's an integration provider. For example, I work with AppDynamics Server Monitoring, and a colleague works with SolarWinds. Another colleague works with Kubernetes. The team works with different monitoring solutions, including Nagios.

Setting up AppDynamics Server Monitoring is easy. It's not hard to implement. It's straightforward and quick, and even the architecture isn't that complex. The solution is easy to implement.

I'm rating the setup for AppDynamics Server Monitoring five out of five because it's very easy. Sometimes, you might find some difficulty, but the support team can help resolve that quickly.

The pricing for AppDynamics Server Monitoring in Africa and the Middle East is too expensive, so it's very hard to sell it to customers. If there could be different pricing or package for the region, that would be great.

My company pays for the license of AppDynamics Server Monitoring on a per-agent, per-server basis. It's $700 to $1000 per server, and it's paid annually. My company is on a subscription model for the solution.

On a scale of one to five, where one is expensive and five is cheap, my rating for the price of AppDynamics Server Monitoring is a two.

I'm using the monitoring solution AppDynamics Server Monitoring.

My rating for AppDynamics Server Monitoring is nine out of ten.

My company is a reseller/integrator of AppDynamics Server Monitoring.

AppDynamics has been decommissioned over time for the newer cloud-native apps, and we have been using more apps. We primarily use a Google native holistic monitoring tool for tracing, capturing, log aggregation, annual infrastructure, and server monitoring. As our applications get modernized over time, we reassess our need to have various monitoring tools. To some extent, cloud-native tools solve a lot of these problems. When we are on-premises, we solve these problems with AppDynamics but things are being done differently in the industry now, and many of these problems are being solved with cloud databases.

We have been using this solution for five to six years. We have a hybrid model, and in the past, we tried to take these tools to cloud, but it was not well suited for our use cases. We were slowly and gradually trying to eliminate legacy items used on-premises.

It is a stable solution, but nothing is a hundred percent perfect, and there is always room for improvement.

We have a hosted application set up concerning the AppDynamics controller, and we don't have any scalability issues. We never even moved to the SAS-based model for AppDynamics, and we have our own hosted environment.

Setting up the monitoring agents was straightforward, and there was no hassle. I don't believe it requires a lot of maintenance.

I am not privy to details around the software product pricing, but if I compare AppDynamics Server Monitoring with JVM-based applications, it is a pretty good tool. Even compared to legacy apps such as .NET and ASP.net, AppDynamics is the right choice.

I rate this solution a seven out of ten. However, we currently lack distributed tracing, and we want to implement it going forward.

We use it for performance and transaction trace monitoring. We use it for .Net and the JVM-related work. We look at all the heat maps and the Garbage Collection to see if there are any failures. 

It gives me the ability to trace logs between transactions, for example, a DB transaction or JVM transaction from one hub to the other. I can easily find out where the problem is or where the bottleneck of the issues lies. 

The overall performance of this solution could be improved. The hot-hot infrastructure features could also be improved. If one goes down, the other should pick up automatically. When we patch one data center, the other primary or secondary center needs to be manually started. We need to do a manual sync between the database and the AppDynamics applications.

I have been using this solution for four years. 

This is a stable solution. The only drawback is that it is not a cluster environment and it doesn't have hot-hot features.

This is a scalable solution but we would like more options to hold more licenses. Right now we have 30,000 agents using this solution.

The technical support for this solution is good.

Positive

Before AppDynamics we used a product called BlueStripe that was acquired by Microsoft. 

The initial setup of this solution is straightforward. The deployment is also straightforward because we used some of the provisioning tools to package the software and distribute it. Creating dashboards and fine-tuning JVMs took some time. 

This solution has really helped us to improve some of the performance of the JVMs at an early point in coding.

I would rate this solution an eight out of ten. 

I work with a global bank that operates across Asia, the United States, and Europe. It's a few thousand people. We primarily use AppDynamics for Kubernetes, web applications, middleware APIs, Java, etc. In terms of technology, it's either Java Spring Boot or some of the API calls, and some of the use cases include continuously checking API availability. 

Some use cases are related to front-end tuning or the user experience across the globe. The applications are used across America, Europe, and some parts of Asia. It's a global system, and user experience is what we wanted to measure. AppDynamics is SaaS. I've never used an on-prem version. The controllers are mostly on AWS, while the agents are deployed on-premises.

Transition tracing is the most valuable is pretty easy and useful, but the user experience piece is also good. 

The Kubernetes cluster agent has not yet matured. That's one area that requires a lot of improvement. You have two options for implementing the Kubernetes agent. One is deployed in DocCloud, but you can't download those images from DocCloud for security reasons at most organizations, so this option isn't that useful.

The installation for the second option isn't that user-friendly. Transition tracing for the Kubernetes application is challenging. You have to navigate to a new set of user interfaces in AppDynamics, so that's the pain point. There is an icon you need to click on to get a newer user interface.

I've been using AppDynamics for almost five years. 

AppDynamics scaled well up to around 3,000 agents. The performance deteriorated after that, while Dynatrace could support more than 10,000 agents. We were surprised that AppDynamics' scalability is not so good.

I had a good experience with tech support. When we raised a ticket with AppDynamics, we usually got a response within a few hours. If we set up a call, their engineers will get on the phone with us. That was also reasonably good. 

Setting up AppDynamics is relatively straightforward except for the Kubernetes part. It was all easy for the Kubernetes cluster agent part. We implemented thousands of agents using Ansible, so it was automated. It was about 15 to 20 minutes in terms of pipeline and restarting because a lot of the scripting and automation were already done. 

The AppDynamics license is divided. It isn't one all-inclusive license. Dynatrace has one agent, but AppDynamics has different sets of licenses. You need to define your use case and what you want to monitor. That is something you need to be clear about. Once you know your use case clearly, take time to figure out your target state metric, and go for AppDynamics. 

I rate AppDynamics seven out of 10. In the modern world, Dynatrace is moving toward helping the companies in the current landscape, but AppDynamics is a second-generation company. It needs to adopt more of a lifecycle perspective rather than limiting itself to triage, tracing, etc.