What is your primary use case for AppDynamics?

AppDynamics is used to monitor multiple applications in our company. Our company recently faced an issue with a mobile banking application. The tool conveyed that many people logged in successfully in the aforementioned application, and for others, the login failed. AppDynamics showed us at our company that the customers on a specific telecom carrier have a problem with the SSL certificate between the mobile device and our company's firewall. In our company, we also had an issue with slow functionality in a mobile application that also belonged to the mobile banking category; AppDynamics showed us that it was an issue with the database, as found in database monitoring. Another use case of the solution is for basic server monitoring such as CBU, disk memory, Network I/O, and similar operations.

I use the solution in my company for application performance monitoring.

We use the platform for infrastructure monitoring purposes.

The main use case for AppDynamics in our company is monitoring and managing the performance of our web and mobile applications. We use AppDynamics to identify and resolve performance issues, such as slow loading times or transaction errors. It also helps us track the availability of our applications and ensure an optimal user experience for our customers. Additionally, we use AppDynamics reporting and analytics to make informed decisions about the scalability and sizing of our infrastructure, allowing us to provide quality, reliable service as we grow.

I use AppDynamics since all of our company's servers, applications, and services are configured with AppDynamics. In case of unavailability or when the servers go down, we log into AppDynamics in our company to check our CPU memory and file system utilization. AppDynamics helps our company understand the availability status of the servers and figure out when the server went down or came up while trying to find any HTTP errors.

We use AppDynamics mainly to monitor the application performance.

AppDynamics is an APM tool. We use it for application performance monitoring for a financial company. It is an end-to-end monitoring solution for any application and works with different technologies, such as Java and .NET. The company was able to monitor their transactions with the financial institution to determine where the problems were in a particular brand. The company was satisfied with the performance of the solution.

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.

My clients use AppDynamics for monitoring the performance and behavior of applications, as well as detecting any signs of potential overload. It also allows them to identify when certain applications are not functioning as expected. Essentially, its primary purpose is to monitor and evaluate the behavior and performance of applications.

We use the solution for performance monitoring such as latency testing to see how long it takes a customer to log in and complete their transaction. If we see any latency we look into the code to see what the issue is and correct it.

We use AppDynamics to monitor application performance.

I use AppDynamics when there's a performance issue with an application, but if it's a network-related performance issue, I use Accedian Skylight.

I primarily use AppDynamics for application performance monitoring.

I mainly use AppDynamics to detect issues and bugs and monitor our enterprise database module.

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.

Our main use of this AppDynamics is to monitor customer applications, such as web applications. For example, to monitor the availability of online stores, and to figure out whether we have any problems.

We use AppDynamics mainly for troubleshooting the database side. If there is any issue that is happening, we go through layer by layer from the start of the application, for example, the UI layer. We go all the way to the database layer to show where the exact problems are. Additionally, we use it for other monitoring and alerting purposes.

We use this product for performance monitoring.

We use the product heavily in our ecosystem. The prime focus for our consumption is for Telkom - a telco and also the mother company. Telkom bought Business Connexion, the company that I fall into. The IT company, BCX, belongs to Telkom. The current real estate that we're responsible for, in Telkom, that we support and maintain on their behalf, is using AppDynamics. We use it for application performance monitoring alongside Foglight, which we would like to replace.

We are using the solution to improve the performance of our application transactions.

I am using this product to monitor all microservice environments. I check all services and performance issues and implement some alerts and dashboards. We are also monitoring all applications that are not in a microservices environment. They are in a WebLogic environment. So, we use it to monitor WebLogic applications, Tomcat applications, and microservice applications that are running in the OpenShift environment or Kubernetes environment.

Our use case for AppDynamics is helping customers with performance problems and applications.

I primarily use AppDynamics for my servers.

We use AppDynamics to evaluate an application we were using. The name of the application was called Liferay and it is an open-source portal, and we wanted to evaluate the performance of our application.

We use this product for the public sector and for really big data centers and infrastructure.

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.

We use this solution to monitor the response time in CPU and usage and for URL monitoring.

AppDynamics is an application performance management solution. We use it for application monitoring, database monitoring. The solution is deployed on public cloud, but the agents are on the servers with the controller on the cloud. I am a Senior Performance Engineer.

We use AppDynamics for monitoring application performance, end-users, and infrastructure. The product has analytics covering all these areas.

AppDynamics can be used for understanding where the bottlenecks are in your environment, and where your applications are struggling. For example, when you have major data collections, you can easily see in AppDynamics, when you have slow responses.

It is primarily on-premises. We've been evaluating cloud, and I've got one application that's using a cloud-based solution, but the bulk of it is on-premises.

AppDynamics is used for performance management. It monitors the application's performance on a monthly basis. I assist in the configuration of AppDynamics, which is used to measure the performance of the application.

We're a bank. We do use the predictive tools for the different products of the bank and the application which the bank utilizes.

We are using AppDynamics for application management.

The big problem we've always had is connecting the dots, so to speak. We've never been able to say that the application is having an issue before somebody calls us and tells us, and that's extremely embarrassing. Plus we're a little late to the table. With AppDynamics, you can be able to tell whether they're having errors or whether they're having a slow response time.

We have an application that we have made which is the core of our business. In many cases, new code comes out or there is older code that gets mixed with newer code and you will see slowdowns or problems that can happen. This solution gatherings all this different pertinent information about how long a particular piece of code sits in what stack of the application. When you have a slowdown or an issue is happening, you can look through the application processes step by step. You can find out where the application was lagging behind. Most recently, we had a problem with some SQL queries that were not optimized in our application. It was taking approximately 30 seconds for the code to get a return. We were able to narrow down where the problem was by using this solution to find out what was taking a long time on that particular query, it turned out to be the DVAs. The DVAs were able to be fine-tuned to make the query a little bit more efficient because we were returning much more data than what was actually needed for that part. We were able to simplify it and it went from 30 seconds down half a second.

We primarily use the solution for effective application monitoring.

We use AppDynamics in our company. I am the IT product manager, who is responsible for the design of the solution. We use this solution for application performance monitoring, byte code injection, and user experience monitoring, infrastructure, and database performance monitoring.

We deployed our agents on the cloud for a Kubernetes application. We get the hardware details from the Azure and AWS monitoring. We import those matrices into AppDynamics and we see all of those details, along with our application performance detail, within the AppDynamics solution. We are not using machine agents because we are making use of the Azure Monitoring and get the matrices from there.

We are using this solution for performance testing and transaction tracing.

We are using it for performance management. We are using its latest version. Right now, we are in the adoption stage. We are going through the training process, and slowly we will start using it. Initially, a team of 50 people will be using AppDynamics. Our goal is that all teams use AppDynamics so that we can benefit from it.

We work in the banking industry and we deal with business transactions, including responses for the users. We capture all of the traffic in our AppDynamics platform. It is a really good application tool.

We are a solution provider and I am a presales engineer. AppDynamics is one of the products that we implement for our clients and have experience with. At this time, I'm using it for training purposes, for the team.

Ability to identify end user performance issues and drill down into root cause to improve MTTR and application availability.

I am using AppDynamics in order to monitor Java applications.

We use this solution to help reduce incidents in our production environment by providing usage and performance metrics, application dependencies like databases, net services, caching, and much more.

We use this solution for application monitoring and the alerting mechanism. We have a complex platform infrastructure, deployed in multiple JBoss Fuse, ActiveMQ, and Data Grid servers.

When you have a lot of AWS products running (and integrations connected to them) the only way you can monitor them is to have a system or automatic reporting. Cisco AppDynamics gives lots of "extensions" that collect metrics and feed them back to an AD controller so you can get a picture of health, usage, rules, and reporting. It also works across environments from cloud to traditional, which means you don’t need something for AWS and then something for in-house products.

We use multiple APMs, but for smaller projects AppDynamics is too cost-prohibitive. It is a more expensive APM among the competitors, which is fine because it also does a lot more on the auto-detection and the AI side. It also supports a lot more languages. So whenever we hit a project that has the budget and the need, we look to use AppDynamics, especially if the technologies are complicated. If somebody has a very simple two-tier Python or Node, we can use almost any APM. When we're dealing with somebody who has 50 or 60 tiers, some traditional stuff, some microservices; some stuff is in containers, some stuff is in real instances; there's Node and there's PHP, and there's a bit of C code in there somewhere. This is where we hit a complex case. It's usually a larger app, an app that has existed and evolved over time with many modules at play, making it almost different products, but it's all one big product. This is the type of case where we look towards AppDynamics because we can just drop it in and have it work. We can't do that with the other APMs that we work with because they just wouldn't work. They'll do this little silo or that little silo, but they won't work with everything. With few exceptions, we have not found any production code that we couldn't make work with AppDynamics.

Java application instrumentation across a microservices architecture build.

We use it for service level monitoring. Currently, we use AWS. Recently, we started using Serverless AWS as we use communities for all our other services. For containers, we use Serverless AWS, and we use databases, like Cassandra Aurora. The product integrates well with all of them.

We are using it for monitoring. Our applications are in AWS, and the monitoring system is part of AppDynamics.

Monitoring log and statistics using graphs to see how we are monitoring our network traffic, and whether systems are healthy or not.

The primary use case is everything related to monitoring.

We use it for break fail detection.

If we have an issue, it is useful for finding the root cause of incidences. So, we use it for troubleshooting.

For monitoring application performance: I worked for a company which concentrates on application performance consulting service. Cisco AppDynamics was one of the tools used.

The primary use case is to monitor our applications and get a handle on any issues ahead of time, such as memory leaks, complete utilization of CPU, and the need to spin up a new server. Being able to know all of these things ahead of time and act on them is a primary requirement. And once an application is placed on top of that, we would also like to monitor what's happening with the application The solution is doing great.

Testing the customer behavior to learn their problems on a website, the heatmap flow, and other information.

We use it to monitor the load testing environment.

Monitor 1000's of .NET, Java, Node.js, and Go applications using an auto-discovering agent-based tool.

Extensive use cases, dozens of primary and secondary use cases ranging from core application monitoring at the global level to micro level performance analysis at the transaction level. AppD provides the ability to also manage total interactions at the web/mobile browser level, the database and core infrastructure including server level and L4 network.