- Business Transaction Tracking
- HTTP Header values
- Introspecting slow and error transaction at different tier levels
- Analytics helps to group business calls based on vendor by using HTTP values
The primary feature we are looking for is tracking async calls because most of our API are async calls. We cannot view HTTP data.
We require a seamless way to upgrade the controller and .NET agents.
The plugins available are tedious to use and not robust, e.g. URL monitoring.
The application(controller) is very heavy on hardware. This increases our cloud cost.
It should be more intuitive and provide better metrics when drilling down in the UI.
This also goes with URL monitoring script provided by community in Git-Hub and also Plug-In repositories on the AppDynamics site. This plug-in is a little tedious to configure because of the YAML file, and only supports HTTP 200 is alive i.e ping request to PORT 80. There's no script for login automation. Again we managed to write custom scripts here for logging using VBS.
There seems to be a certain disconnect between the AppDynamics development and support teams. Maybe because this is a developer intensive engineering tool and support guys need to understand the framework of .NET or a Java ecosystem and applications that cut across various design architectures. This could be a gap which AppDynamics needs to bridge.
I have used this solution for one year.
The controller slows down with Windows platforms.
Sometimes the MySQL process of the AppDynamics controller takes lot of memory and the controller hangs, despite configuring it as per requirement.
Since the application is agent driven (client side), if we need to upgrade the .NET agents on 100 servers, then we need to visit 100 servers to upgrade or deploy them.
The technical capabilities of people sitting in technical support is questionable. The reason being this is an engineering tool for application instrumentation both for .NET and Java. We have asked queries and also raised some issues. For most of the issues, especially regarding tracking async for .NET API, we never received a solution. Also, some configuration issues where primitive in nature but not resolved immediately.
The technical documentation contradicts technical support.
We started using version 3.8 of the tool, and since then, I don't see many changes on the support side.
No, we didn’t use anything in the past for application monitoring. This was the best out there in the market as per evaluation by market research. The tool was a good fit when we did a POC.
Initial setup was complex.
Setting up configuration to track the metrics is little tedious.
Understanding the metrics numbers is little confusing as they contradict, e.g. The number of API calls displayed on the main screen is different than on the analytics screen.
A normal user would find it difficult to understand and read the metrics, because too much drill down is necessary, and the numbers are difficult to interpret and relate to the problem.
Implementation was done in house. The tool is configuration intensive. A good development and operations team need to know the application dynamics to configure this application.
Since it’s high on budget, it’s recommended to buy a developer license and play around with this tool in a dev environment and then procure for production.
I don't think premium vendor support is required for setup and configuration.
We haven’t reached the stage where we calculate ROI, as we are in the early stages of onboarding customers. We can probably gauge this once we have a sizable number of customers on board, which will take time. Measuring ROI will be calculated by using the API call tracking by customer and also the turnaround time (time saving) in the early stages of development cycle.
The pricing is way too high, especially with the analytics feature and end-user monitoring.
They have separate licensing offerings for development and production.
The best option is to get into an engagement for a few months before procuring this tool.
This is purely an application instrumentation and monitoring tool with good features for business analytics.
It is probably more integrated and works well with Java application, as some features for .NET don't work.
Host the AppDynamics controller on a Linux machine with a medium or high profile. A Windows server machine would show symptoms of disliking it within 2 to 3 weeks of setup.
It is not comparable with infrastructure tools. The plug-in available to track infrastructure-related activities are not stable and not robust.