Aternity AppInternals [EOL] Reviews

The application side of the solution is its most valuable aspect. We are using it on the logs that were captured on the application side. 

As an Administrator, before we bought this AppInternals, I didn't have visibility on why items were slow or why an application was not running. This gives us the ability to see what's going on. The application is load balancing. We can now see if its own server has issues or just one specific server has issues.

Right now, our challenge is that we don't have the support we need, and based on the requirements we have, there are some audits and it turns out that the AppInternals agent is causing false trafficking issues.

We could not update the server requirements on the version we have right now, due to the support. 

It would be great if the solution could offer fixed bundles and more features.

The most valuable aspect of this solution is the integration with their other systems. It's easy to understand and it points out the relevant problems in the enterprise.

I would like for it to have automated updates, the way the product updates itself should be all automated, as opposed to what it is now. 

We primarily use this solution for troubleshooting. Whenever a customer has problems in the performance with the servers, we use this application to manage this do some troubleshooting to fix the problem.

The most valuable feature is the connections for marketing. I like it that one can match IPs with the application name.

Cuts down on the time to resolve complicated application issues. We have been able to trace individual transactions to identify where the issue is whether in the application code, server or network.

Transaction Tracing is the most useful. Being able to have the transaction stitched together so we can see where the problem is has proven invaluable.

I was part of a Test Organization (focused on Performance Engineering) and TTW allows our engineers to provide many more improvements opportunities to the developers while improving software performance. It was not just saying where the problem was, but the tool was an enabler for more technical people to nail down the root cause of problems and propose better solutions. After the tool was installed in applications, the confidence of the team improved towards raising more specific performance defects.

This product has really wonderful features and one of the most valuable ones is the transaction searches into TTW. This will show you the operations that occurred under conditions that the user specifies, giving you the opportunity to drill down on the things that are more important and affecting system performance.

Besides that, the capability of analysing each individual transaction captured to a very low level detail (method call/line of code). This ability empowers the testing teams to provide more visibility to developers on how they can improve.

We really like the dashboards and their latest release. By going to v10 it made our lives a whole lot easier because prior to v10, we had to put all of these assets, these Riverbed arguments, basically JVM start up itself. Then when they send out a new release or a new patch on it, the library changed to 64-bit. If that library changed, we have to go to all the different JVMs we have implemented and we would have to go in there and change all of the start-up arguments. When we go with system wide enabling, we don't have to mess around with the JVM arguments anymore. We just control on the backend of AppInternals what we want to instrument and what we don't want to instrument. That makes it a lot easier.

One thing that I can't do with the AppInternals - we have put in a request as an enhancement that we would like to search for items. If we're searching for a URL and we want to know was it a get or was it a post.

Those are attributes that are of interest to us because we can have a static URL but rather than just seeing the performance time, the metrics and everything around that, we needed a way to go in and carve those out. To find out which one was a get and which one was a post. We would like to see those columns. We would like to have those columns available that the customized columns had.

With v10, Riverbed has done a very good job and we've been using it a lot. There's actually more features in v10 that we really haven't gotten into yet. I'm planning on making some more time to dig into those.

The product is very useful to find problems in middleware for the application servers, especially agent instrumentation and management is user friendly. The main point for me is that there is no overhead on the application servers.

The Active Dashboards is valuable because we can show the results to all the related business units and then they can follow end2end system monitoring side to track it themselves.

The biggest problem of end-to-end APM monitoring is that service assurance is mapping a problem to the appropriate team. When the business units check their jobs, step by step, every single system seems to work properly but they need to check the big picture, which AppInternals does easily.

We can see problem trends before they affect customers and quickly drill down to where the issue is located. This eliminates support silos and allows various support teams to work together to quickly resolve the problem.

There are several valuable features, including:

• Seamless interaction between the various products;
• Ability to identify slow web pages, slow network/application transactions and drill down to offending packets, code, SQL statement, web service, network devices, or systems;
• Dashboard allows for "single pane of glass" monitoring of application and network performance; and
• Synthetic transactions, WMI and SNMP query capability.