Splunk AppDynamics Reviews

We use AppDynamics Browser Real-User Monitoring to monitor the performance of applications. We use the solution to see the errors, snapshots, and exceptions in the backend and front end of our applications. We also use AppDynamics Browser Real-User Monitoring for frontend monitoring, end-user monitoring, checking the response time, and other frontend metrics. We also use the dashboard in AppDynamics Browser Real-User Monitoring and also use the solution for sending error or issue alerts to our clients.

The best feature of AppDynamics Browser Real-User Monitoring is that it lets you find errors in synthetic jobs ahead of the users. The solution shows you all front-end metrics. You can also see JavaScript errors and jQuery errors through AppDynamics Browser Real-User Monitoring. You can also do a correlation between the front end and the backend, or from the user to the navigator, to the backend through the solution.

What could be improved in AppDynamics Browser Real-User Monitoring is for the synthetic jobs or synthetic agents, in particular, you can't do a lot of tests with just one agent. You have to install a lot of agents if you want to do more tests, so this is an area for improvement in the solution.

Another area for improvement in AppDynamics Browser Real-User Monitoring is that you're only able to see basic metrics in the absence of server or database visibility.

For the SaaS version of AppDynamics Browser Real-User Monitoring, my team just downloaded then installed the extension in an application in Azure to see the application on the controller, so if this can be done in the on-premise version of the solution as well, without needing to install the agent on the machine, then it would make AppDynamics Browser Real-User Monitoring better. Currently, the .NET agent consumes the CPU or memory and clients usually raise this issue with my team, so it would be good if the on-premises version doesn't require agent installation on the machine.

Another functionality I'd like to see in the next release of AppDynamics Browser Real-User Monitoring is for it to receive updates from the file config without needing to reset IIS because right now when you do a modification in IIS, you have to restart IIS. When you add a service to the agent config, you have to restart IIS. For the product server, it's not possible to reset IIS after you make changes to the config file, so if this could be improved, then it would make AppDynamics Browser Real-User Monitoring a better solution.

I have about two years of experience with AppDynamics Browser Real-User Monitoring.

AppDynamics Browser Real-User Monitoring is a stable solution.

AppDynamics Browser Real-User Monitoring has good scalability.

Support for AppDynamics Browser Real-User Monitoring is always available. My team does a lot of Webex with support. Whenever you have a problem with the solution, you can always contact support.

As a developer, I have no idea about the pricing for AppDynamics Browser Real-User Monitoring. Another team is in charge of the licensing for the solution.

Currently, AppDynamics Browser Real-User Monitoring is deployed on-premises, but my team is also testing its SaaS version.

My advice to anyone considering AppDynamics Browser Real-User Monitoring is that it's a very important product because you can use it to troubleshoot and detect errors in your applications.

I'm rating AppDynamics Browser Real-User Monitoring as ten out of ten.

On-premises

We were using an ID integration, and we were monitoring and using the EPM, et cetera. AppDynamics is able to provide us with in-depth insight into the bottlenecks in the system.

It allows us to understand what is causing latency in the system. Using AppDynamics, we can drill down to the code on which the bottleneck is seen, and the developers can fix the issues, increasing the overall application's performance.

The tag and follow aspects are very good. Basically, how the transaction is moving through various servers. We can see everything via a dashboard, a visual dashboard, that can showcase transactions.

It's pretty stable.

We can scale the solution as needed. 

We'd like to see features that could support IBM's Integration Bus. AppDynamics is unable to provide the details for all the flows in the system transaction flow. That component needs work.

The initial setup is a bit complex.

It was quite expensive.

I've been using the solution for two years. 

We only really run into issues during the upgrade process. Other than that, it is stable and reliable. the performance is good, and there are no bugs or glitches. 

It's a scalable product. If a company wants to expand, it can do so. 

We have between 150 and 200 users right now. We do not have plans to increase usage. 

Technical support has been helpful in general. 

Positive

We were using DynaRisk. However, it did not meet the needs of our use cases. 

We found the initial setup to be a bit difficult. It's not perfectly straightforward. 

There are two or three people on hand that can handle deployment and maintenance tasks.

We handled the setup ourselves in-house. We did not need any outside assistance.

We have not really noted any ROI.

It's a very expensive product. Each of the licenses after this month for one server is around $9,000 or $10,000. Therefore, monitoring one server concerning analytics or server monitoring is pretty expensive.

Before beginning, a new user should take time to understand the product. They need to analyze a few options and see which best fits their use case and go with that. There are many on the market to look at, including DynaRisk and DataDog.

I'd rate the solution seven out of ten. 

Public Cloud

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. 

On-premises

The tool provides more insights, but maybe if in the recommendation section, we can use some AI tool for the optimization of the database, then it would be helpful.

With AI, it would be good if the tool could help us with the database optimization part. If my company can get product support, it would be great since the tool has the ability to make predictions based on the database performance that something may be going wrong and notify us of the precautions to be taken.

I have been using AppDynamics Database Monitoring for two years.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a nine out of ten.

The tool is used by four to five people.

Whenever my company interacted with the solution's technical support or engineers, we had a better experience compared to the ones we had with other tools. I rate the technical support a nine out of ten.

Positive

The product's initial setup phase is easy since a separate machine is required, and it is not directly installed on a database as it is a type of proxy. We collect the logs, which is a model that is pretty easy to handle.

The solution is deployed on an on-premises model.

The solution can be deployed in a day or two.

Cost saving in terms of not an HR-based perspective, but I know that some performance improvements are there. The tool helps in overall cost optimization. Maybe we are not making decisions to increase the database and its resources. Once we know that there are some performance issues, then we can fine-tune the tool and save on the costs. The costs for my company have been reduced by 15 to 20 percent using the solution.

The tool is expensive. If one is expensive and ten is low price, I rate the product price as seven out of ten.

I know about two products. AppDynamics Transaction Analytics was already a part of AppDynamics solution when my company bought it with an enterprise-level licensing, so it provides some business analytics dashboards. The other product I use is not related to analytics, so I didn't use it much.

In terms of optimizing our company's data operations, the tool provides insights on whether there are any challenges in databases or if there is something related to queries, which is helpful. One can monitor the performance and see if there are any delays that occur in the databases when we are dealing with the queries, and it helps to find out what the issues are.

I don't know what the features of the tool are for performance analysis, but when any application generates codes to extract particular information from a database, it sometimes gets stuck on some queries. At the query level, monitoring and providing more insights are beneficial.

A scenario where the real-time monitoring aspect of AppDynamics was crucial for our team was when we were adding a new application and testing it with our production environment or in the UAT; the tool was helpful because we could fine-tune the application and optimize it. If there are certain issues, we can easily identify such issues with the tool, especially when adding a new application since the product helps a lot.

Speaking about how the alerting system in AppDynamics helps in preventing potential database issues, I can say that from my observation, if there is some problem at a certain point in time, we get alerts, but I am not sure if prevention to help us identify issues is available or not in the tool. It would be good if we can identify the issues before it affects our company. There are some slow performance areas that need to be identified.

My company often takes care of the maintenance of the tool. One engineer can maintain the tool.

I recommend the tool to others.

I rate the tool a nine out of ten.

On-premises

We analyze data for performance and availability, which is produced by servers, infrastructure and cloud. However, it's not sufficient to only use Dynatrace because it makes a lot of data. This data is interpreted by AppDynamics automatically with technical data to understand the business impact, thus improving productivity. In Europe, enterprises widely use SAP, and AppDynamics effectively supports this by monitoring the core IT environment and the services around SAP, like CRM, Salesforce, and logistics systems.

The alert mechanism in AppDynamics enhances server management tasks by using agents installed on each server. These agents capture numerous metrics, collaborate to describe specific transactions, and allow us to monitor each transaction based on user interactions. We can see where any transaction might falter in the SAP server, application server, or presentation database, helping us identify the exact point of failure or degradation in transaction time, extract anomaly detection, or pinpoint real failures in SAP or other applications. This mechanism is very similar to Dynatrace, but AppDynamics is currently the best option for SAP.

AppDynamics Server Monitoring lacks investment in new technologies like Kubernetes and cloud solutions. Dynatrace has received significant investment in these areas and is better suited for cloud-native applications. However, AppDynamics still holds value for traditional applications used in banks or larger companies.

I've worked with AppDynamics Server Monitoring for five to six years. My experience in monitoring systems started around 2020-2022, focusing on serviceability for SAP ERP environments.

Regarding stability, I would also rate it at nine out of ten as it is highly stable.

I'd rate the scalability of AppDynamics Server Monitoring at nine out of ten, indicating it's highly scalable.

AppDynamics Server Monitoring is deployed based on the organization's needs. For instance, installing it on a single server is better for a few clients for on-premises deployment. On the other hand, different solutions are available for cloud monitoring applications. The trend is shifting towards new paradigms like DevOps. AppDynamics adheres to these standards and can be used for both on-premises and cloud environments, depending on the specific requirements and business model of the organization. Maintenance requires a dedicated team, which can be extensive, especially in large organizations like banks.

I would rate my experience with the initial setup of AppDynamics as seven out of ten.

The return on investment with AppDynamics Server Monitoring has been significant in certain areas, especially for SAP environments. However, there hasn't been as much focus on the broader market due to their emphasis on cloud messaging applications. It ultimately depends on the customer's specific needs and how well the solution aligns with them.

The pricing for AppDynamics is expensive, but it is possible to negotiate special pricing through bids.

AppDynamics Server Monitoring is integrated into the infrastructure through agents installed on the servers, and it utilizes REST APIs for process control and integration with other solutions. In terms of AI usage, AppDynamics uses AI for anomaly detection and resource forecasting.

AppDynamics Server Monitoring is recommended, especially for SAP environments or cloud-native applications. However, the recommendation depends on the specific needs of the organization.

Overall, I would rate AppDynamics Server Monitoring as seven out of ten.

We use the platform for infrastructure monitoring purposes.

There could log management features included in the product.

We have been using AppDynamics for one month.

AppDynamics is a stable product. It doesn't have a lot of bugs. We can fix the bugs at a code level whenever we encounter them with our expertise. It provides an ease of installation as well.

I rate the platform's scalability an eight out of ten.

Dynatrace works better compared to AppDynamics. While using AppDynamics, we have to install different external agents for managing, customizing, and monitoring logs. In comparison, we must install only one agent to carry out the processes while using Dynatrace.

The initial setup process is easy once learned. At the moment, I am a new AppDynamics user and am exploring more ways to make the process easier.

The product is more expensive than Datadog but lower than Dynatrace.

It is a wonderful monitoring tool that manages various aspects such as system resources (CPU, RAM), mobile performance, and infrastructure monitoring. It provides ease of use, alerting capabilities, integration support, and scalability. Thus, it is already maintained. It doesn't provide log management services; we have to install different types of agents for business processes. It is not a cloud-native platform like AWS, GCP, etc. I rate AppDynamics an eight out of ten.

We use AppDynamics mainly to monitor the application performance.

The most valuable feature of AppDynamics is its ability to track the transactions between different applications.

AppDynamics should improve its ability to track all the transactions.

We have been using AppDynamics for approximately three years.

AppDynamics is a stable product. We rarely had any issues with the solution.

I rate AppDynamics ten out of ten for scalability.

Getting a response from the solution's technical support team is harder and takes longer. Since the solution has a structural support model, it requires some layers of escalation to get the correct response.

Neutral

The solution's initial setup is easy. However, it is harder than Checkmk because it needs to install the agent.

The solution's initial deployment takes about three to four months. However, it's a work in progress because new applications are added every time.

AppDynamics is an expensive solution.

AppDynamics is deployed on-cloud in our organization.

Overall, I rate AppDynamics a nine out of ten.

All the features are useful. When it comes to application monitoring, AppDynamics Browser Real-User Monitoring provides smooth connectivity to different applications. There is an EEM module that is highly visible and ensures a good user experience when customers access their applications on the cloud for a long time. In general, the features are a good fit for our operations.

In user monitoring, AppDynamics Browser Real-User Monitoring should provide a better user experience. It needs to offer an end-to-end experience, including the internet layer and third-party elements that come into play on websites. Instead of focusing solely on the performance of the application web layer, it should have the inclusion of other domains like the internet, DNS, third parties, and caches that affect the user experience.

There should be more options for more options for customizations to third-party visibilities.

Another area of improvement is faster support. The response time could be faster. 

I've been using AppDynamics for five years. However, we do not use the very latest version.

Even in terms of stability, AppDynamics have fine-tuned features. They provide frequent updates, twice a year. So the product is pretty stable. 

I would say the stability of AppDynamics is an eight out of ten. 

You can easily scale it. So I would say the scalability of AppDynamics is an eight out of ten. 

AppDynamics is quite a mature product. You can even increase the scalability without affecting your environment.

Customer service and support are pretty good. The aligned support and customer support experience is quite good. If you raise an issue or a request, they will get back to you within the estimated time and resolve it for us. 

Neutral

I have explored other options. There are other solutions in the market, like CatchPoint. But the problem is we wanted an end-to-end solution that integrates well with our existing systems, and AppDynamics fits that requirement.

The initial setup depends on the environment. For example, if a customer wants a secure setup, I would say it's moderate, not overly complex. 

If a customer doesn't prioritize security policies based on the security architecture and they don't care much about it, then it's an efficient tool. 

I would rate the initial setup a five out of ten for the average user, where one being difficult and ten being easy. Five is the highest rating I would give. It's more towards excellent, I would say.

We have it on-premises because that's where we can slice and dice and offer to the customer. That's what I suggest. If it's ISPs or CSPs, it should be on-premises. If the customers want, they can go with SaaS.

The deployment time varies from company to company. If it's fast, it probably takes a week to get it up and running. But if it's on-premises, it takes around four weeks.

Just two people are required for the deployment. If it's not an existing timeline, then it may require more people. If it's an existing timeline, then it may require more people.

The implementation does matter based on how many applications you want to monitor and how complex those applications are. If it's an on-premises setup you want to pursue, or if it's a SaaS version you want to pursue. All these factors contribute to the overall resourcing. So, how do you want to add into it? If we take a simple scenario, like a single application with two tiers, I would say two resources are more than enough. But if it's on-premises and you have twenty-five applications and a timeline to achieve it within three months, then more resources are required. That's how it works.

AppDynamics Browser Real-User Monitoring is costly. If I have to rate the pricing, I would say seven because it's really expensive, with one being low and ten being high.

The pricing needs to come down. Many customers find it expensive, so that's why I'm rating it a seven.

If you want to have end-to-end visibility into your applications, from users to endpoints, I would recommend using AppDynamics Browser Real-User Monitoring. It's also a good choice if you want visibility into customer conversations.

Overall, I would rate the solution a seven out of ten.