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.

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.

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.

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.

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.

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.

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.

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.

We are using this solution because sometimes there is a technical requirement for a correlation between server assets and application assets. The end users are happy to use the solution for some applications related to .NET to get correct information.

We use the solution for business-critical applications as an application and server monitoring agent. The users use the solution to correct their application’s performance and clear hurdles in their applications.

The product provides a nice end-user experience. The users are happy to use the product for .NET applications. The users are happy with the real-time use cases.

I would like to see more information about utilization. The tool should provide information like the number of connections and processes utilized in real time.

I have been using this solution for the last four to five years.

The solution is perfectly stable. I rate the stability a ten out of ten. There is no need to do anything after the installation or configuration.

The product scales perfectly. I would rate the product’s stability a ten out of ten. We have four to five very critical applications related to revenue transactions used by more than 50 to 70 employees, including line management, domain leads, SMEs, L1, L2, and L3 employees. We use the solution once a month, depending on the requirement.

I have not found any issues in the last four to five years. It's a very smooth and easy setup. I have never got any errors or issues from the end user.

We have multiple solutions related to server monitoring. We have HPE and other tools as well. Compared to other tools, AppDynamics gives correct and good information related to the server. We switched to AppDynamics because we required a correlation between applications. That's why we use the same tool for the application and the server.

The product is very easy to set up. I rate the ease of setup a ten out of ten. The installation and configuration are very easy to learn.

It would take hardly half an hour to deploy the solution. It's a process that revolves around end-user requirements. First, I validate the details of the requirements shared by the end user. Then, I validate and deploy the solution according to their requirements. The deployment is done in-house. One person can handle the deployment.

We have also deployed SCOM. We decided to use AppDynamics because we required a real-time output during peak hours. We used Appdynamics to share the information with the users.

We have a very limited use case related to server monitoring. There is no need to refer to further addition. Every piece of information related to server monitoring is very concrete and crystal clear. We do not get any requests in any division from the end user related to the product. I do not have any issues with the configuration.

I would recommend the product because it provides real-time information. Other tools only provide information when there is a server issue. If the CPU reaches 80% while the threshold is set at 70%, they receive an alert. However, Appdynamics offers real-time monitoring and allows users to check their server utilization instantly. Other tools do not provide a consolidated UI to the end users.

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

AppDynamics Database Monitoring has multiple use cases, including long queries, database performance, and database query details, which we have shared with the operations team.

There are multiple uses related to performance. The first is the DB connection tool, in which we have shared the details related to application performance and DB performance enhancement. In most cases, they have checked their connection, sizing and acted accordingly. For the long query details, they have performed their queries, reduced the time, and enhanced their performance.

The features related to the application performance in AppDynamics Database Monitoring are the most valuable. AppDynamics Database Monitoring has corrected its application-level code and enhanced its application performance.

The application end of AppDynamics Database Monitoring needs to improve by checking which applications consume licenses. We are not getting any details from the AppDynamics Database Monitoring portal. AppDynamics Database Monitoring's agent details must be enhanced, so each agent needs to show what kind of technology is being used. I would like to have agent details from AppDynamics Database Monitoring.

We are not getting related information and agent details from AppDynamics Database Monitoring. For example, if we have one hundred APM licenses and have onboarded multiple applications, there are no details about which technology uses which kind of agent.

Other solutions have one agent that gathers information on all kinds of server components. However, with AppDynamics Database Monitoring, we don't have any universal solution related to application instrumentation, server performance, stats, server component stats, and service stats. We would like to have better server components.

I have been using AppDynamics Database Monitoring for more than seven years.

AppDynamics Database Monitoring has high stability. I rate AppDynamics Database Monitoring a ten out of ten for stability.

I rate AppDynamics Database Monitoring a ten out of ten for scalability. More than 1,500 people are using the solution in our organization.

AppDynamics Database Monitoring provides high-quality technical support.

Before AppDynamics Database Monitoring, we used a different solution. We switched to AppDynamics Database Monitoring for multiple reasons related to end user experience.

AppDynamics Database Monitoring’s initial setup needs to be made easier. I rate the solution’s initial setup a five out of ten.

We implemented AppDynamics Database Monitoring through an in-house team of three members. AppDynamics Database Monitoring’s deployment takes around five to six hours. We get the information from the end user related to their application architecture, and according to that information, we plan and perform the implementation.

AppDynamics Database Monitoring does not require any maintenance. I highly recommend others to use AppDynamics Database Monitoring.

AppDynamics Database Monitoring's end-user experience is very good. The solution's tool navigation is very simple and clear-cut. Also, the error and exception detail AppDynamics Database Monitoring shared are crystal clear.

Overall, I rate AppDynamics Database Monitoring a ten out of ten.

We use AppDynamics Database Monitoring to identify high spikes in critical data, which helps us better understand when applications stop responding or are not responding well.

The solution can be deployed on-premises or in the cloud.

Data monitoring is the most valuable feature.

The price of the solution has room for improvement.

I would like the solution to be more customizable to meet our client's requirements.

I have been using AppDynamics Database Monitoring for two years.

I give the stability of AppDynamics Database Monitoring an eight out of ten.

I give the scalability of AppDynamics Database Monitoring a nine out of ten.

The technical support is excellent.

The initial setup is straightforward. The deployment takes two weeks and requires one architect and one developer.

We implement the solution for our clients.

The pricing is average. I give the price a five out of ten.

The license is paid on an annual basis.

I give AppDynamics Database Monitoring a ten out of ten.

We require five people to maintain the solution.

AppDynamics Database Monitoring only requires users to have a basic understanding of databases.

I use it to solve issues that my clients encounter, such as application slowness. It helps me identify whether the issue is related to the database, server, or CPU memory management.

Moreover, I use it to find solutions and provide recommendations to my colleagues.

This solution not only provides answers but also provides sensor data. This allows us to quickly resolve issues that developers may take a long time to solve. In essence, it helps us address problems at an early stage. Moreover, it is especially useful in production servers where real users encounter numerous issues.

There are numerous issues that arise during peak times, and AppDynamics makes it easy for us to identify the problem areas and determine the appropriate resolutions. This is how it helps us find solutions effectively.

Regarding improvements, I believe the dashboard could be more optimized. Although it claims to be optimized, I think it should be even more convenient, especially for advanced users.

Additionally, the documentation can be a bit challenging. It would be beneficial if the documentation provided clear solutions for every problem. In my opinion, the documentation could be improved.

I worked with AppDynamics for around three to four months. I have been working directly with it for the past year.

I use the latest version.

It is stable, but the only downside is the licensing part. Other than that, it's a reliable product with no major issues.

It is highly scalable. There are no additional limitations in terms of scalability.

In my company, we have around 50 to 100 clients using this tool. Although it can be a bit expensive, it is still being used extensively to solve various problems.

It's straightforward, not too complex. However, it requires proper learning to effectively use it.

The deployment process typically takes around one to two hours, depending on the system. Once the setup is complete, we can proceed with the implementation process.

First, there's a need for basic knowledge of OS, especially for Windows and .NET. Additionally, understanding concepts like Dynatrace and AppDynamics, their functioning, and architecture is crucial. These are the key methods involved in the deployment process. If it's a cloud solution, then AWS or Azure are the recommended options. If it's on-premises, then using either Linux or Windows is ideal.

For deployment, we need to focus on event configuration, which involves learning about network events and configuration. Once we understand this, we can proceed with the deployment setup. There is no frequent deployment. In case the deployment is not satisfactory, we may need to learn about Linux and Windows concepts.

I have seen some ROI.

It is an expensive solution. It's on a yearly basis. We need to pay for it annually.

I have used Dynatrace. The main difference between the two is that AppDynamics utilizes different data mechanisms, while Dynatrace uses a unified agent approach. This simplifies the complexity of Dynatrace, providing more visibility and root cause analysis. In terms of benefits, AppDynamics is more scalable than analytics.

Overall, I would rate it a nine out of ten.