91制片厂

What differentiates Splunk AppDynamics from other similar products?

It provides deep code-level diagnostics, allowing developers and operations teams to pinpoint the root cause of performance issues quickly. This feature is crucial for efficiently troubleshooting and resolving issues within the application code.

What is your favorite aspect of this product?

It offers comprehensive user experience monitoring, allowing organisations to understand how end-users interact with applications. This includes insights into response times, user journeys, and the overall quality of the user experience.

What do you dislike most about this product?

It has a steep learning curve.

What recommendations would you give to someone considering this product?

Consider starting with a pilot implementation in a controlled environment or with a specific application. This allows you to evaluate the effectiveness of AppDynamics within your context before deploying it more broadly.

What differentiates Splunk AppDynamics from other similar products?

its easy of use also auto discovery for outside calls and requests and application flow map were very different from others i remember also the application performance baseline was great feature with alerting

What is your favorite aspect of this product?

Flow Maps

What do you dislike most about this product?

maybe reconsider pricing

What recommendations would you give to someone considering this product?

its unique tool to discover your application/DB or middleware bottlenecks its will discover production performance bottlenecks and anomalies better than any other APM tool

What differentiates Splunk AppDynamics from other similar products?

AppDynamics is a great tool for monitoring infrastructure, such as servers, databases, API endpoints, and business operations. AppDynamics is easy to configure; all I have to do is set up an app on the infrastructure I want to monitor, and it will connect to the application, such as Spring Boot, by simply specifying the level. I can define alerts and exceptions, as well as actions that should be taken when triggers are activated, such as sending emails or running scripts. All these make this product differ from other alternatives.

What is your favorite aspect of this product?

AppDynamics flow maps are wonderful; the best part is that everything is displayed in a graph and is easy to understand due to the baseline that we set based on the various apps and demands, which can also be changed at any time. To exceed expectations I can also adjust the notifications to receive them from numerous channels, allowing us to anticipate any problems with any program. I can also create alternate panels based on our requirements, which are frequently incredibly useful. Most likely features are described but there are also more good features in it.

What do you dislike most about this product?

It appears that getting started without basic instruction is difficult. The user interface is simple, however, using the functions is not as simple as it appears.

What recommendations would you give to someone considering this product?

The app dynamics board is useful to me since it provides statistics from the application鈥檚 performance matrix, which helps me determine whether there is a technical issue. Appdynamics helps us prioritize the solution to the problem. Because it is efficient, I particularly like the Appdynamics user interface. The granularity of telemetry data and signs that may represent a developer鈥檚 mentality is a major advantage.