AppDynamics vs Nexthink

• 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

• Ease of data gathering
• Consolidation of multiple data points into one (previously, you'd have to request one thing from SCCM, one thing from JAMF, maybe something else from your Domain Controllers)
• Support. Nexthink has always provided great levels of support when needed.

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

• The Finder is great but to utilize the product effectively it takes some getting used to. Very 'right click' heavy.
• Learning curve. Nexthink is very boolean based in their investigations (not a knock, most products are), but since they can track things at such a siloed level it's important to know specifically how they are classifying their objects (ex, a package vs. an application vs. an .exe vs. a binary) so you can understand what findings you're getting.
• Parity on Mac and Linux products. This is improving though.

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

• Nexthink has been invaluable at quickly finding application roll-outs that could negatively affect our environment, in most cases before users even report them.
• Nexthink has helped us consolidate and gain visibility in our environment, further standardizing naming conventions, hierarchies, etc.
• Nexthink has integrated with our ITSM solutions, and is easy to use such that technicians no longer feel the need to request data from Engineers, they can just directly get it from Nexthink.
• There is a learning curve, so for good ROI you're going to need to invest the people and training hours to use Nexthink to it's fullest effectiveness. Note, that even a cursory use though would reveal a lot about your environment that will keep you busy.

Read full review