AppDynamics vs Riverbed SteelCentral AppInternals

• Giving a network map of our application that shows where slowdowns are occurring and where network traffic is running into a bottleneck.
• We are able to gather node-specific information that shows the number of sessions a web server or even Redis session statistics.
• We use AppDynamics to give a holistic view of our application allowing us to quickly narrow in on problems.

Read full review

• Try to end application downtime.
• Optimize and improve troubleshooting.
• Detect and identify existing problems.

Read full review

• Price of the AppDynamics is high. But it has many valuable features. This makes it difficult for small businesses to enter.
• Functionality is overkill for most small to midsize businesses (SMBs). When stacking up product units, it can get pricey for enterprises as well.
• With fine granular configs and customizations available, it will also mean that it is very complicated and requires a certain amount of knowledge before we can make full use of all features in the product. Much careful thought and planning is required to get the most of it. Set-up will be longer. One recommendation is for features to be better documented.

Read full review

• Cost - Riverbed is really proud of their products, and the price shows.
• More "point and click" repair opportunities.
• Integration with Cisco DNA, tell which devices could have issues based upon the IOS version, etc.

Read full review

• AppDynamics isn't cheap, but it definitely helps to ensure our applications and APIs are up and running without issue. The alerting is usually good but occasionally mixed, for example sometimes flagging a single error as a critical issue since the API is usually completely error free.
• The cost saving in terms of trouble shooting and analyzing issues in production is fantastic - to know about issues before they are reported by customers enables you to be proactive in resolving them and ensuring maximum up time for our applications.

Read full review

• 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 analyzing 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.

Read full review