On this page:
Search the Database Monitoring topics:
Watch the video:
- You can run additional backup Database Agents that take over for your primary Database Agents in case the primary ones go offline, ensuring your databases are continually monitored despite agent failure or during planned machine downtime. The additional Database Agents can run on the same machines as the primary Database Agents or on different machines.
- You can have an agent in each distinct network of your environment. Since the agent requires network access to the database, you may need multiple agents to monitor all the databases in your environment.
- You can have multiple Database Agents running under different user accounts on the same machine, which is particularly useful if you want to monitor SQL Server via Windows Authentication as various users.
How AppDynamics Monitors Databases
AppDynamics Database Monitoring sorts database activity by efficiency, showing you the worst performing activities. You can immediately see potential problems, such as which SQL statement or stored procedure is consuming system resources, which machine is experiencing lags, and which programs are causing the bottlenecks. For example, AppDynamics for Databases shows how much time is spent fetching, sorting or waiting on a lock.
AppDynamics Database Monitoring polls for running queries and statistics to build a complete picture of what is happening on the database instance. This information tells you exactly what is active within the instance and most importantly what SQL statements are executing. The depth of data collected from AppDynamics Database Monitoring is comprehensive and allows detailed drill down. An expert DBA can view the resource consumption profile of an instance, drill into a performance spike, and then find the underlying root cause within seconds. When your SQL code is running well, AppDynamics Database Monitoring shows this without requiring you to analyze configuration parameters and metrics.
Events Service Dependency