Splunk AppDynamics Reviews

I get information related to application transactions on a day-to-day basis and manage their capacity augmentation according to transaction details. We collect errors and exceptions from end-user applications, and we share the details with the application development team that works on the application errors and exceptions to resolve and create enhanced performance with the help of Splunk AppDynamics. We have been working with Splunk AppDynamics for the last six years.

The main feature for Splunk AppDynamics is the application drill-down, and the application users utilize it with the help of the next blank panel on their application. An application developer, with the help of Splunk AppDynamics, collects data to get the correct information related to their application code and how the application code performs under low load and high load. Once they get the correct information through Splunk AppDynamics, they will enhance their code to perform better under high load.

It is a very user-friendly tool, and I have used multiple tools related to APM technology, not only Splunk AppDynamics. We have multiple tools, but end users prefer to use Splunk AppDynamics because their portal navigation is very simple and clear.

Application owners build down their application performance through Splunk AppDynamics. Based on the information related to daily, weekly, and monthly metrics, the application development team receives related information for their application performance, and they try to resolve application errors and exceptions, which is achieved via Splunk AppDynamics to enhance their performance.

There is a policy related to dynamic performance to baseline, and end users check their application performance according to their baseline, gathering information about their performance. Based on that information, they take corrective measures related to their applications and resolve issues and errors.

The use case for Splunk AppDynamics is mostly for performance monitoring.

I've been using it since 2019, and Splunk AppDynamics has been a very good tool from the beginning. While I haven't seen many new features, it has improved in various places, particularly in identifying transactions and pinpointing the nodes and other applications it uses, such as Apache Kafka or other third-party applications. It clearly creates a mapping of the transaction. It is also more dependable and reliable. I have also seen a couple of extra features for analyzing the transaction. It goes more in-depth in some areas.

The effectiveness of the auto-discovery and mapping in visualizing my application ecosystem is almost perfect. Although it could be improved further, it is currently in very good shape, allowing performance testers to check exactly what is going on, where the transaction is going, where it's spending time, or failing.

My experience with the application performance monitoring capabilities of Splunk AppDynamics has been very good because it gives me all the data I need and provides a very friendly interface, allowing me to showcase any issues to the customer with ease. The feature to copy a hyperlink to the specific timeframe or transaction I want also makes my job easier by allowing me to pinpoint something to an architect or any participant, who can open it up on their screen and easily understand the issue due to the friendly user interface.

Line-of-code-level troubleshooting feature is very helpful. I have used it a couple of times, and it allowed us to diagnose which part of the code seemed to have the issue, although it did make mistakes and didn't pinpoint the errors exactly in some cases. Overall, it's a very nice feature.

Splunk AppDynamics' digital experience monitoring affects my ability to optimize user experience in a very good way because the results I get often need to be transferred to other stakeholders of the project. The friendly and good user interface allows me to show them what I mean by the results and my analysis.

Splunk AppDynamics’ infrastructure monitoring is very good at correlating infrastructure and application performance.

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. 

Our use case is in the lower environment. We are not using it in the production environment. We are part of the performance testing team, so we monitor the users on this server through performance testing, and during that time, we use all the agents, install them on the server, and monitor any bottlenecks. We use Splunk AppDynamics for deep dive analysis and provide inputs to the team. That is our use case.

We are using it only for the on-premises environment, but we are exploring options for Azure-hosted applications and AWS-hosted applications.

Splunk AppDynamics helps us in identifying bottlenecks and providing fine-tuning recommendations. We have many sites. We do deployments and analyze products. Before, as a performance testing team, we were not in a position to tell the team where the issue was happening, only able to provide numbers. With Splunk AppDynamics, we can pinpoint exactly where we need to concentrate and provide recommendations for fine-tuning. Without it, it was a nightmare. We wouldn't have been able to provide this information. 

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.