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.

On the dashboarding side, it's very difficult to do dashboards on the database portion because they don't let you include a lot of the elements in dashboards. They should give a bit more functionality and add more views from the database side. Other than that, all the clients I've worked with are very happy with it. It had everything they needed. No one had any complaints. Only on the application portion, do people get very confused if they're not tech-savvy, but on the database side, you usually work with tech-savvy people. So, the database and the elements are great.

The challenges that we face are all performance based, relating to business transactions, not database monitoring.

One of the key features that are missing is the ability to manage users centrally, which is a real pain when it does not happen. That is a feature that their main competitor has had for quite some time. I'm surprised they don't have it already.

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

The license model is a bit complex. They should make it a little bit easier, which I believe they will do in the next quarter, or in the next two quarters. I also dislike it because it is based on CPU, which will increase the cost of deployment and licensing. They currently have a complex model and charge on a per-node basis. They plan to change this in the future to make it less complicated, but it will be more expensive because it will be done on a CPU basis rather than a node basis. And this is not good. I deducted one point for that.

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.

It would be helpful to have a dashboard and artificial intelligence for error detection and correlation for future releases. 

AppDynamics Database Monitoring could improve the price of the solution, it is costly.

AppDynamics Database Monitoring would be improved with more support for microservices architecture.