We use APM to monitor our production, our QUAIL Java environments, and our web framework environments.
It is heavily utilized. It functions very well. We look forward to new features, because as technology grows we look to incorporate some of that newer technology in our monitoring solutions as well.
We use this for ticketing. This helps us to realize not only from the monitoring standpoint, but we make custom dashboards for our development areas so they can understand how busy traffic affects their application with traffic. They can see how traffic directly affects their application in positive or negative ways. It gives immediate feedback to know, when we have a bad day, we have to look at this area because that slows down first.
It shows us where our weakest link is.
Our ability to know how our application is performing in real-time.
Client-side JavaScript monitoring, so we can have that end-to-end from the client all the way back to our host areas.
Stability could actually be helped because it is a wrapper or an agent on our system. If we are having a bad day in production or if other resources are being utilized, then we will get get gaps in our monitoring system. It does not happen very often, but it usually happens at the worst possible time.
I do not think we have had any problems with scalability. Other than right now it is just for Java agents. It does not have much JavaScript client-side monitoring.
Our monitoring team has used them and would need to be the ones to evaluate them.
I have heard good things. We work very closely with CA. We are a very large customer, so they get back to us pretty promptly.
I was not involved in the initial setup. We have had the solution for years.
I was also not involved in the upgrade setup. I was involved in a lot of the testing of the upgrade processes to make sure that it suited the needs of not only the development departments, but also the applications they monitor.
I think it is above a lot of the other monitoring solutions that are out there.
I would give it an eight out of 10, only because I know the ins and outs of the application. I know its capabilities and strong points. I think it has room to improve.
It could be that we have it configured in a way that is not advantageous. However, it is also upgradability to it is a project instead of a patch. If it was actually an automated process to where it just fed updates to our product that would be great. Now, we have to spin up an effort to actually upgrade the solution. I think cost of upgrading holds us back from getting to the latest and greatest, where if it was more patch level, it would be easier for us to use those newer features.
Make sure to look for interoperability and ease of upgrade. Just because they have the solution, what is it going to cost to maintain the solution, because that is the cost that is hidden down the road.
Most important criteria when selecting a vendor: Of course, they have to be competitive on cost. Always. But now, it has actually shifted towards interoperability with other solutions. We have to have open APIs that are easily tied into so we can actually hook them up to our existing pipeline features.
Its good observation that there is no option in CA AMP where we can identify that how our application is performing in Real time. BUT we have good tool in market like . Net vision, Omniture, Blue Tringle .