What is most valuable?
I like the real-time alerts. Basically, whenever the server goes down due to resource limits, such as JDBC connection pool resource limits, you get to a critical warning as a real-time alert. That's really good. Whenever an absolute restart happens on JVM, it sends a real-time alert, lights, mains, SMSs, and everything.
Also, for the dashboards and reports service, we’ve configured custom transactions. Based on that, we can see which particular transactions are getting more errors and slower performance, which gives us a chance to fix them.
How has it helped my organization?
It has really helped us in troubleshooting. It's like you're taking proactive action, so before it happens, you come to know, "Okay, there's something going wrong." We can minimize the effects of failures by taking proactive action.
What needs improvement?
The main improvement I would like to see is in reporting. If you set it to send daily reports, it just takes a snapshot of the report and sends it to us. For example, we want to see all the events that happened, including exceptions according to the timeline. It just gives you the first page. If you want to go to the second page, you need to get into the AppDynamics console and then go scroll down, replace, scroll down.
What do I think about the stability of the solution?
Stability is pretty good.
What do I think about the scalability of the solution?
Scalability also is good. It's little glitchy, but otherwise it scales and it really gives a lot of information.
How are customer service and technical support?
Technical support is slow. Basically, we mail, we wait, we mail. But I think depending on the priority they take immediate action, because if it is a production server getting affected, they come immediately. So it's really good. If it's development related or research or configuration, they come a little later, but it does not cause problems.
Which solution did I use previously and why did I switch?
There was nothing before basically. We have this in-house application, and if we saw some exceptions, we sent out email. That was how we used to do it before installing AppDynamics. But that was only at the application level. At the server level and JVM level, we did not have anything.
We also have a third-party application called Splunk.
How was the initial setup?
I was not involved in the initial setup. I am the application side, so the configuration admin side is a different group. Once they install everything, that's where I get to pitch in and configure everything on the application side.
Which other solutions did I evaluate?
We looked at Dynatrace, but AppDynamics had much better features. I was on vacation at the time, so I was not there. I was not involved, but I was told that Dynatrace did not have many features. AppDynamics is a lot better. Industry-wide, it's a leader, so they went with that.
What other advice do I have?
In choosing a vendor, one issue is the business impact should be minimized. Because of AppDynamics, we came to know where the bottlenecks are in the infrastructure by using the system agent, as well as the JVM agent. We code mostly with Java. That really helped us to know where to concentrate, and where to troubleshoot, and where to take action to minimize the impact on business.
I would go with the AppDynamics, because they have new analytics and new features coming, which will really helpful. Log analytics allow you see the performance metrics and at the same time, what is happening. The data is in the logs. It really helps and minimizes troubleshooting and the release cycle is minimized.