Splunk AppDynamics Reviews

The main use cases for it are similar to APM from Broadcom.

Splunk AppDynamics is very similar to APM. The part of the database is interesting since users can do many things with this dashboard, and the business dashboards are also very interesting. The main dashboard, showing all communication between components or business transactions, is very interesting as well.

This is similar to APM from Broadcom. The most important thing is managing the performance of the application for critical business in organizations, and it's very important to do this with the solution you want. If you don't have this kind of application, it's impossible to know what happened with your critical business.

It's similar to ABM from Broadcom. It's important to have. You need to be able to manage the performance of the applications that are critical for business in an organization. If you don't have this kind of application, it's impossible to know what's happening with your critical business aspects. 

It is used as an APM. We utilize Splunk as a SIEM for security and infrastructure observability.

What I like the most about Splunk AppDynamics is the end-to-end observability for the application, along with traces. It enhances productivity and aids in cost avoidance.

Normally, we require end-user monitoring for our digital banking services. Since we operate in the financial sector, we need monitoring for our mobile apps and web browsers, particularly for our online banking systems. This is our main use case.

The feature that I appreciate in AppDynamics Browser Real-User Monitoring is the intuitive and user-friendly dynamic mapping it creates for workflows. The application flow presents a streamlined interface, making it easy to navigate across different interfaces and troubleshoot applications. This interface is particularly valuable for identifying and resolving application issues effectively.

AppDynamics is used to monitor multiple applications in our company. Our company recently faced an issue with a mobile banking application. The tool conveyed that many people logged in successfully in the aforementioned application, and for others, the login failed. 

AppDynamics showed us at our company that the customers on a specific telecom carrier have a problem with the SSL certificate between the mobile device and our company's firewall.

In our company, we also had an issue with slow functionality in a mobile application that also belonged to the mobile banking category; AppDynamics showed us that it was an issue with the database, as found in database monitoring. Another use case of the solution is for basic server monitoring such as CBU, disk memory, Network I/O, and similar operations.

The transaction snapshots are the most valuable feature of AppDynamics. I find this feature valuable because for every transaction running through any application server that is detected by AppDynamics, you can check the code that makes the flow list and an issue, which can come from any functionality, and in our company, we can utilize the saved time for troubleshooting and reduce the time to repair and the developers can enhance the security and functionality. 

The performance and DevOps teams use the solution to drill down and find out the root cause if we are getting any high response time. In that condition, we have drilled down and checked out the calls and methods, which are taking too long.

The solution's most valuable feature is the response time from the end-to-end server. The solution is user-friendly and easy to use for everyone.

We are using this solution because sometimes there is a technical requirement for a correlation between server assets and application assets. The end users are happy to use the solution for some applications related to .NET to get correct information.

We use the solution for business-critical applications as an application and server monitoring agent. The users use the solution to correct their application’s performance and clear hurdles in their applications.

I am not a user, I am an implementer.

For EUC, one of the use cases would be to monitor online shopping from retail, for example, to understand the client's journey and if they are experiencing any difficulties in, at the very least, making their purchase or browsing, the front-end of a specific customer's online shopping.

The second would be internal applications to determine whether the application is living in an order that allows it to process its workloads. It's quite generic because we have so many different types of applications.

With Real-User Monitoring, the most valuable features are what I have described. We can see the customer's path from their computer to the backend systems. It gives us full visibility end-to-end, and if there are any issues, we can observe and record them to improve application performance quality. In addition to the EUC, you can add synthetic transactions, where you can see from every point if your application is performing adequately in terms of reachability if you are running a global site.

I work with a global bank that operates across Asia, the United States, and Europe. It's a few thousand people. We primarily use AppDynamics for Kubernetes, web applications, middleware APIs, Java, etc. In terms of technology, it's either Java Spring Boot or some of the API calls, and some of the use cases include continuously checking API availability. 

Some use cases are related to front-end tuning or the user experience across the globe. The applications are used across America, Europe, and some parts of Asia. It's a global system, and user experience is what we wanted to measure. AppDynamics is SaaS. I've never used an on-prem version. The controllers are mostly on AWS, while the agents are deployed on-premises.

Transition tracing is the most valuable is pretty easy and useful, but the user experience piece is also good.