I get information related to application transactions on a day-to-day basis and manage their capacity augmentation according to transaction details. We collect errors and exceptions from end-user applications, and we share the details with the application development team that works on the application errors and exceptions to resolve and create enhanced performance with the help of Splunk AppDynamics. We have been working with Splunk AppDynamics for the last six years.

The use case for Splunk AppDynamics is mostly for performance monitoring.

The main use cases for it are similar to APM from Broadcom.

Splunk AppDynamics is very similar to APM. The part of the database is interesting since users can do many things with this dashboard, and the business dashboards are also very interesting. The main dashboard, showing all communication between components or business transactions, is very interesting as well.

This is similar to APM from Broadcom. The most important thing is managing the performance of the application for critical business in organizations, and it's very important to do this with the solution you want. If you don't have this kind of application, it's impossible to know what happened with your critical business.

Our use case is in the lower environment. We are not using it in the production environment. We are part of the performance testing team, so we monitor the users on this server through performance testing, and during that time, we use all the agents, install them on the server, and monitor any bottlenecks. We use Splunk AppDynamics for deep dive analysis and provide inputs to the team. That is our use case.

We are using it only for the on-premises environment, but we are exploring options for Azure-hosted applications and AWS-hosted applications.

It is used as an APM. We utilize Splunk as a SIEM for security and infrastructure observability.

Normally, we require end-user monitoring for our digital banking services. Since we operate in the financial sector, we need monitoring for our mobile apps and web browsers, particularly for our online banking systems. This is our main use case.

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.

The performance and DevOps teams use the solution to drill down and find out the root cause if we are getting any high response time. In that condition, we have drilled down and checked out the calls and methods, which are taking too long.

I'm familiar with agent-based database monitoring. It easily integrates and monitors various databases like Oracle, SQL Server, MySQL, and PostgreSQL, with minimal configuration. There are also some advanced, AI-infused use cases.

It's better to enable additional metrics and custom metrics if needed, depending on the specific application.

For business purposes, the analytics side is a very unique part of the APM solution. There are lots of different APM products in this ecosystem, but other than AppDynamics, there is no business insight or very limited capacity. Other APM solutions on the business side are limited. Most of our bank customers and fintech customers use the Analytics side with very high priority.

From the C-level perspective, they mostly do not care about the operational metrics, for example, response time, CPU memory, or different kinds of technical metrics. They focus on the business side. The business impact of their application: Is it good? Is it healthy? Is their revenue increasing or not? Or stable? With the business analytics side, we provide a hundred percent of this business info. Before their end-to-end process, we provide real-time business metrics. 

For example, one of our banking customers uses business analytics to measure real-time ATM transactions, how much their customers withdraw or deposit from the ATM machine, or maybe POS machine, or in Europe, SEPA and SWIFT transactions. Customers manage their transactions from another site. We also measure real-time money transfers.

From each level, for example, ATM side, Internet banking side, mobile banking side. The business analytics side is the further version of an APM product for all APM products.

We worked on the kernel, and being able to monitor our application is important. We have utilized some predictive analysis, and that seems to be the biggest advantage.

We use the software for proactive incident detection, root cause analysis, and fine-tuning.

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.

We use the product to optimize application performance by monitoring database transactions and extracting insights for troubleshooting issues.

Our primary use case involves performance monitoring of applications. We use it when an application is deployed, and we need to monitor it from a performance testing standpoint and engineering standpoint.

The solution effectively detects anomalies in the system.

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 use case involves evaluating a mobile application's performance and user experience. We seek insights into peak usage hours, the application's status, and that of secondary services, such as databases and APIs, to gauge the mobile user experience.

We also want to identify potential bottlenecks and mobile degradation. We aim to ensure that mobile user monitoring is effective, similar to other forms of user monitoring. Although mobile devices present a different medium, they aim to detect errors, service degradations, slowdowns, and other issues. 

The solution offers a real-time view of the things happening in a database. 

My company uses AppDynamics Server Monitoring for end-to-end application performance monitoring. The solution is integrated with the database managed by back-end and end-user teams.

Our customers typically leverage Browser Real-User Monitoring for a variety of purposes. Primarily, they seek to gain insight into end-to-end user experiences. This entails tracking user interactions comprehensively, from frontend actions to backend system responses. They desire seamless correlation between user-triggered actions and the subsequent journey through various backend components such as servers, databases, and APIs. Additionally, they aim to contextualize this data within the broader environment, encompassing infrastructure status, network health, and application performance. Ultimately, they prioritize the ability to view these interactions as cohesive transactions, facilitating efficient troubleshooting and optimization efforts.

We use the product to monitor some of our critical systems. We started using the solution for application performance monitoring.

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 are monitoring lots of different databases with AppDynamics Database Monitoring, such as Couchbase, SAP HANA, DB2, Oracle, MySQL, MongoDB, and Postgres. 

In Turkey, most companies push their workers to work with the on-prem side because the government regulation is very strict. So 97% of my customers are working on the on-prem side, although we have three accounts working with the SaaS solution.

We use it to monitor the end-user responses of Oracle and Microsoft SQL. We still use OEM for deep dives.

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.

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.

I am the coordinator of the implementation of AppDynamics in our customers' companies. 

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

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

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

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.

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.

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

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.

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

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.

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

I am not a user, I am an implementer.

For EUC, one of the use cases would be to monitor online shopping from retail, for example, to understand the client's journey and if they are experiencing any difficulties in, at the very least, making their purchase or browsing, the front-end of a specific customer's online shopping.

The second would be internal applications to determine whether the application is living in an order that allows it to process its workloads. It's quite generic because we have so many different types of applications.

We use AppDynamics mainly to monitor the application performance.

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.

We use the solution to monitor transactions and to keep track of, like, data analytics.

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.

We use AppDynamics to monitor application performance.

My company uses AppDynamics Server Monitoring for server monitoring and end-to-end monitoring. The tool has an event alerting mechanism that lets people within the company know when any server is down so that you can raise a ticket, and the support team can work on that ticket.

Our use case depends on whether the client has revenue on their primary revenue-generating websites. For example, we previously implemented for Aviva Financial, and their primary revenue-generating website was their Aviva website. They primarily do home, medical, motor, and car insurance and use this solution to download insurance quotes. This solution is also used to monitor the end-user activity, website speed, product details and quotes.

We use the solution for end-user performance monitoring to monitor customers' browsers, like Chrome, Safari and Internet Explorer. So we're able to get details, and each transaction gets monitored, and the information gets captured and presented to management.

The management observes the end-user activity, which helps get quotes signed and monitor the payment system gateways.

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. 

Because AppDynamics sells this as end-to-end visibility, there are no use cases in the databases. Use case applied to AppDynamics Brower Real-User Monitoring can be applied here as well. If the user experiences latency on its request, it's most likely because the database is effectively queuing the request. The same scenarios can apply.

We use this solution to monitor our core application's performance, to know what transaction is running an error on transactions in these applications. We are based in Egypt and are customers of AppDynamics. I'm the deputy general manager of the company. 

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.

Our company uses the solution to track abnormalities and check connections for critical applications.

We had the solution on-premises but recently moved it to the SaaS platform. 

We are using many business applications, and the backend databases are very critical for them. So, everybody's using AppDynamics Database Monitoring.

The main uses of this solution are dependent on our clients needs. They are mainly in the banking sector, and use the product to measure user experience, or for analytical, business IQ purposes.

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

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. 

We are currently using AppDynamics Database Monitoring on-premise but we are migrating to the cloud.

We are using AppDynamics Database Monitoring to understand where the long queries are, and how your applications are performing against the database. You can actually see whether it's a database issue or if it's an application issue. Additionally, you can run explain plans against it, to see which queries need to be optimized.

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.

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.

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 use AppDynamics for end-to-end monitoring solutions. Our organization is a crowd BPO and we have deployments in 128 countries.

It's mainly used to monitor both applications and databases. That's primarily how I use it.

Essentially, I use it for monitoring. I perform performance testing and use it to monitor database performance, CPU usage, and generate alerts on different nodes based on CPU utilization and other factors. It's mainly used to check the performance of the nodes.

We use AppDynamics Server Monitoring to keep track of live errors, loads, calls per minute, etc.

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.

We use AppDynamics for monitoring purposes to check up on CPU health and application health status.

AppDynamics is used to monitor the health of our applications. If any application is down and linked up with AppDynamics, we can see it on the AppDynamics console. We can identify when a specific process went slow and the exact issue. Additionally, if there is any high CPU utilization or other issues, we can figure it out using AppDynamics.

It is very helpful as we can also make custom alerts in our system for specific issues like high CPU utilization or application downtime. We can even customize the alerts to be sent to a particular email domain for automatic notification, so there's no need to monitor it 24/7.

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.

Application Analytics is mainly used to get full visibility into the SAP stack in order to detect performance problems.

I use AppDynamics Database Monitoring to monitor application performance.

I primarily use AppDynamics for application performance monitoring.

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 are using AppDynamics Database Monitoring is used as a performance monitoring tool for any application. 

The solution is deployed on-premises and on the cloud. It has a software gate in several legacy software, and they have part of the application in the cloud. AppDynamics is able to deliver cloud information.

We have 774 small cities, and all the cities have agencies who use the system. We monitor all of the agencies. There are eight million consumers who access these systems on a mobile device and millions of transactions per day.

We're a partner and reseller for AppDynamics. We had a bank that we had to monitor from start to finish. We did the bank, and I then moved on to another product, but one of my mates is still busy working with AppDynamics.

Most of it was on-prem. We did some product testing on the cloud, but the client at that stage didn't have much on the cloud. Connecting to a cloud was quite simple as well.

AppDynamics Mobile Real-User Monitoring is an application performance management tool.

The platform itself is divided into different modules, each of which can be enhanced with additional modules. We work with End User Experience Monitoring, both server monitoring, and application performance monitoring.

AppDynamics Mobile Real-User Monitoring is used to monitor user experiences when evaluating and deploying applications for the company.

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.

We use this product for performance monitoring.

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.

It is very useful to monitor user behavior and see the user experience.

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 primarily use the solution for effective application monitoring. 

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 are using the solution to improve the performance of our application transactions.

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

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.

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 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 are using this solution for performance testing and transaction tracing.

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 use this solution for database monitoring, application processing, and performance monitoring. Within our business unit, there are hundreds of people using this solution.

AppDynamics was implemented to help us with some performance issues. I'm not a big fan in terms of other features compared to some of the other tools that we use, but when it comes to end-user monitoring (where you want to capture or trend back business transactions, or where you want to really view the performance of the tools), It's not just good in terms of managing your production system, but some of the developers use it to tackle performance issues and get ahead. 

I have a B2B eCommerce website and we have some business transactions. For that, we have configured the business transactions in AppDynamics. Apart from that, we have a list of servers that we have configured in AppDynamics, to send us some sort of alert if there's something bad or the servers are in disguise or something.  

First, we use it to handle the business transactions alerting, and then the servers alerting. And second, we use it to create the dashboard so that we can get real-time updates on how the system is performing at around runtime.

The primary use we have for this product is application performance monitoring for mission-critical applications. We are a reseller.  

We implemented AppDynamics to have a clear, real-time monitoring solution for our critical business systems. 

We have two tenants; one for production and the other for our quality control environment. We are using more than fifty probes, including application and database probes.

Our company is worldwide, across geography. We are using the public cloud deployment model.

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.

We use the on-premise deployment model of this solution. 

Our primary use case of this solution is for monitoring our critical applications. The automated data dynamics enables us to monitor the performance of an application and unknowns.

We are using this product for application monitoring.

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.

AppDynamics lets you monitor applications and databases and provide a unified view of your infrastructure. You are able to monitor a single point but this would not be useful and with this solution, you would not use it this way. You want to monitor how your application is impacted from the application perspective to the backend, through to the server infrastructure, database, hardware, network, and application labs. It is all able to be monitored by AppDynamics. It monitors all the aspects from the infrastructure up to the user, and the application.

We are using AppDynamics for application management.

There are various use cases. For example, one of them can be for a mobile bank. Mobile banking is something that is being used more and more with customers. Based on the fact that the architecture of applications is being more and more complex and more and more distributed while having a deep view of what the user is experiencing on the mobile or on the browser. It's really valuable. This is true especially for a bank, as the user experience really explains or defines the services. You want the mobile bank to work quickly and you want it to be stable and you want to basically perform all the actions within seconds, not over 10 seconds for every action.

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 use the product for enterprise-level monitoring, everything from application to database monitoring. The product will tell you everything. It will show you at the code level where the issue is. For example, the solution will analyze a database and it will tell you which of the CPUs are taking more time to execute, showing exactly where the issue is.

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.

In terms of our use cases, we monitor cloud instances and application instances. When we do performance testing, we monitor all the metrics, like server-side metrics, as well as the client-side metrics. If it is a browser with real user metrics, mobile user behavior kind of things, we'll monitor it as well. 

We are a reseller and AppDynamics is one of the products that we sell to our customers.

Our customers use it to gain insight into performance.

We use AppDynmaics Server Monitoring to monitor and gain insight into what is happening in our infrastructure.

With this solution, we see traditional use cases with companies that have a digital business model, such as insurance companies, travel or banking companies. It's really for where they have an application that is critical for the business and that brings in revenue. And when these applications are not available, they lose money.

For example, in the tourism sector, when you want to book a flight or just about anything, and the app is too slow, then the use case is quite easy to calculate because clients leave the page, go and find alternatives and don't come back.

Most of our customers are midsize and enterprise companies, it's not really a solution for small companies. We are an IT service provider and a Cisco partner, and we represent and invest in AppDynamics. I'm the Director of Application Performance Management.

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

What we do in general is analysis on the application side. When we have slow SQL requests we jump on the database monitoring to see, for example, the total time the request has been pending in the database. We can solve SQL requests by their pending time. 

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.

I am using AppDynamics in order to monitor Java applications.

We primarily use the solution for monitoring the transactions of our user's in-app purchases. 

The primary use case of the solution is for end-to-end visibility for all applications we choose to monitor.

We primarily use the solution to check how the database is performing and to log and check queries.

We were testing this solution and wanted to do application monitoring for our websites. 

We primarily use the solution for monitoring. We are monitoring the customer experience of our banking solutions for external customers.

Our primary use for this solution is troubleshooting.

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.

We use it for break fail detection.

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.

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

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.

AppDynamics allows users a complete application monitoring solution for making better products/applications.

The primary use case is everything related to monitoring.

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.

We use it to monitor the load testing environment.

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

The primary use case is application performance monitoring. It performs well.

For customer journey monitoring: Stitch together complex journeys involving the entire ecosystem (internal through external IT) and multiple stakeholders.

It is an excellent product for application performance monitoring.

We use the product to monitor servers and CPUs and the amount of storage through VPN connection for 55 branches of our customers distributed across countries.