AppDynamics Database Monitoring pros and cons

The product requires high maintenance.

The synthetic scripting for end-user monitoring could be a little bit broader. Instead of using just Python, they can include a few other languages so that not everyone has to jump on the bandwagon for Python and do Selenium scripting. They can open up that a bit to make it simpler for people to do the scripting.

The application end of AppDynamics Database Monitoring needs to improve by checking which applications consume licenses.

AppDynamics Database Monitoring would be a better product if it could support new technology, such as cloud technology. Even Dynatrace lacks support for newer technologies.

The day-to-day activities should be less complicated so that anyone can manage it.

I believe they need to increase their level of visibility in the infrastructure, particularly in the infrastructure monitoring section, which currently lacks visibility.

It could be more user-friendly for beginners.

I have found it sometimes a bit difficult to trace the transaction all the way through to the application. I'm not sure if that problem is on the database side or on the application side, but that would be something that I would like to be improved. The traceability from the application to the database, sometimes, is a bit of a challenge. If you're using AppDynamics, with the Java agent, for instance, you need to be able to trace it through.

The major concern lies with reports, specifically their configurability. It's like, if I want to combine multiple reports and generate them all at once, that's not possible. Even though there's a setup for generating 25 reports, I wanted to group them all and generate them in one go, which isn't currently feasible. I have to manually run each report and set the time for it.

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