What is your primary use case for AppDynamics Database Monitoring?

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.

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.

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

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

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

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.

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 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 are using this product for application monitoring.

I use AppDynamics Database Monitoring to monitor application performance.

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'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.

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 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 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.

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.

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

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.

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 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.

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

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