Please share with the community what you think needs improvement with AppDynamics Database Monitoring.
What are its weaknesses? What would you like to see changed in a future version?
An improvement could be if the monitoring was able to be summarized into something more clear and simple for people who don't have the technical skills on the database side. The solution needs to have some prepared dashboards on the database. When we use AppDynamics we have a lot of screens and we have to jump from one screen to another. It would useful is if, on the database, monitoring required merely a click on a button and then you have the monitoring dashboard that you can display for easy access.
AppDynamics needs to consolidate their technology agent types into one agent that could be deployed on any host no matter what the technology is that it is running. It is really the implementation of AppDynamics that is very difficult because it is very manual. They really need to improve upon that and do more to simplify user processes. So, I would like them to have a single agent type instead of an agent-based on the technology. I think that having a single binary agent that you can put onto any host would make it a lot easier to work with.
I'm only working as an administrator on the solution, so I'm not in a position to really discuss too many technical aspects of it. The application monitoring needs improvement. It needs to be easier for someone who isn't a proficient developer. For example, if we use Java for monitoring events to gather history-based data in regards to the application, it should provide a better core-controller. When we monitor any Java application, the approach for us is to identify a set of classes as part of Java programming. These particular classes needs to be executed so any end-user using AppDynamics would be able to see the culprit class. There shouldn't be a need for a final report. Yet, we don't have a feature like that at this time. A person who is monitoring everything needs to have very good knowledge about the solution and not everyone is a proficient programmer.
We also use Oracle Fusion and the actual tracing of your transactions on Oracle Fusion is difficult because they use an asynchronous type of tracking between the nodes. It makes it difficult for AppDynamics to track. The user access management could be a bit better.
The solution should add some monitoring similar to Oracle monitoring tools for databases. Oracle has a lot of features to monitor SQL queries, and make some recommendations to resolve them. AppDynamics is just monitoring for delays and doesn't provide any recommendations. It's a deficiency.
The monitoring of different schemas within the database could be improved. They should split the dashboard into different schemas, instead of having one.
We are having a problem where one of our tenants has had issues with availability over the past two months. There is a lot of downtime for the SaaS tenant. Based on the user experience feedback that we have had, I think that the most important thing to improve is the availability of the SaaS, the cloud environment. The mobile application needs to be improved. We are evaluating a solution from SAP, and we are interested in is seeing the integration or the interface, and what we can get out of these new probes. We had a conference call with AppDynamics and challenged them to resolve the SAP solution monitoring so that it works side-by-side with our critical applications.
The solution could improve the server size for AppDynamics to include middleware products, which it doesn't yet cover. If they add middleware for sophisticated sites, AppDynamics would be the global choice.
* Synthetic monitoring of applications and products in a better way would help to improve the product better. * More OOB reports also would help.