Splunk AppDynamics Reviews

I am using Splunk AppDynamics for application support and production support. I have worked for an alert system, which monitors any failures in the application related to alerts, job failures, and any services not working, by setting up all the alerts in Splunk AppDynamics to ensure the application is running fine. If it is not running fine, we can identify which service is not running and why it is not running, allowing us to monitor every log from Splunk AppDynamics. In the first case, if you want to see logs, especially regarding what and how, just keep the keywords according to the exception, and you will get all the details related to that. It is very easy to find solutions based on those logs. Additionally, if the application is not stable and is expected not to run for another hour, we have the option to check for space-related issues or any database tablespace-related issues. Splunk AppDynamics allows you to set up every kind of alert to proactively monitor and stabilize the application.

We are using the secure application feature in Splunk AppDynamics. To explain how that affects our ability to detect and protect against vulnerabilities, if anyone attempts to send an email to UPS.com using certain keywords related to transactions, Splunk AppDynamics immediately triggers and alerts for phishing attempts. This setup was also configured by the development team. I am aware of the features, such as if anything suspicious arises, many keywords need to be inserted to receive alerts, for instance, when someone tries to break into your security or network.

I use two or three applications that can be accessed from mobile. Once I connect to any public network—such as TFL rail—my mobile disconnects immediately, preventing me from logging in for two hours, due to restrictions set up by my development team. The importance of providing my mobile's MAC address to the development team that has integrated everything into Splunk AppDynamics ensures every team member's device is monitored to track connections to public, private, or secure networks.

The most important aspect of Splunk AppDynamics is that every service can be monitored to determine if it's running or not. If there is an issue, a red pop-up appears immediately, and you receive an alert. Based on that alert, you can also set up a ticket, so you will get a ticket as well. This is the best feature because, although you can't monitor a whole application at once, Splunk AppDynamics gives you the option that if there is any failure—simple failure regarding anything set up as per our use cases—you will get an alert. That alert helps us significantly to quickly find the solution or root cause of any issue. It is very easy to understand where the issue is, which is the most beautiful feature of Splunk AppDynamics.

Splunk requires significantly more improvements compared to Splunk AppDynamics, specifically regarding the licensing aspect. Splunk renews licenses every six months, which is inconvenient. It would be better to have a one-year license to avoid needing to update keys constantly, which can only occur on weekends, making it a burdensome task. Although Splunk is better for certain use cases, Splunk AppDynamics is broader in functionality. Specifically, I want enhancements related to creating dashboards not only for logs or minor services but also for configuration levels, allowing us to check configurations immediately without manually opening the entire code when exceptions arise—a feature I wish to see improved in Splunk, although it may not be necessary for Splunk AppDynamics.

I have almost six years of experience in digital experience monitoring.

Regarding deployment, it is neither overly easy nor extremely difficult, as we spent over two months getting it set up. Initially, when nobody had prior knowledge, I joined the team and shared my documentation. While it is not simple, some familiarity with the process is necessary.

The stability of Splunk AppDynamics rates as the best, providing a minimum score of nine; ten is seldom given as there are always areas for improvement, but Splunk AppDynamics is superior to any alternative, including Dynatrace. The vast array of options available further supports this.

Splunk AppDynamics is user-friendly, with many options readily available, primarily through drag-and-drop features. Setting up configurations is straightforward in Splunk AppDynamics, as it is in Splunk. Nevertheless, app-wise, Splunk AppDynamics is superior. A crucial aspect is that when working shifts alone, you can constantly monitor Splunk AppDynamics; upon any error occurrence, you receive immediate notifications. You can click on alerts, which lead you to specific issues and guide you to find logs and services that may not be functioning. If needed, you can easily restart them. Although several nodes run simultaneously, should one fail, passing processing responsibilities to other nodes is possible with Splunk AppDynamics. In contrast, with Splunk, it requires manual checking and restart, which is a significant drawback relative to Splunk AppDynamics. It's an incredibly user-friendly tool that anyone can master in a month.

When rating the technical support, Splunk primarily serves log-related queries effectively, with limitations. It excels in returning standard log information and locating issues quickly, but Splunk AppDynamics allows for monitoring entire applications at every node, making it superior for horizontal scaling.

Dynatrace is also a highly popular product alongside Splunk AppDynamics. Earlier, we utilized Splunk, but it has some limitations when compared to Splunk AppDynamics. We previously switched to Splunk AppDynamics due to the limitations faced with Splunk. Splunk AppDynamics supports monitoring six to seven applications simultaneously on a single dashboard without needing to create numerous dashboards for different applications, which is a real advantage. Dynatrace, while similar to Splunk AppDynamics, does not exhibit clear superiority over it, as they are competitive products.

The purchase was made directly from Splunk AppDynamics, as we have direct licenses from our vendors, including Quest software and Microsoft.

In my team, there are nine members who utilize Splunk AppDynamics.

Time is the most valuable aspect as I work in the banking sector. When issues are rectified promptly, we save money. In the production environment of a bank, timing is critical, especially with a one-hour SLA, and analyzing issues takes time. Splunk AppDynamics significantly aids us because as soon as we identify a problem, we immediately receive API call insights through the AI version currently in use, suggesting resolution pathways and options such as restarting the server or application. I estimate a minimum of 30 to 40% time savings, as if one person is working a shift independently, they do not need to rely on others due to the dedication to specific issues. Immediately upon discovering an issue, Splunk AppDynamics AI provides numerous solutions. We typically find about 40 to 50% of solutions instantly after identifying an issue, plus alerts guide us to the precise location of the problem. Overall, as a production gatekeeper, we achieve at least 50% efficiency immediately, with potential savings ranging from 60 to 70% as well, reinforcing why it is a popular tool in the banking industry.

I consider Splunk AppDynamics to be cost-efficient.

I have been using Splunk AppDynamics for more than six years. Regarding the data collection feature with agents or open telemetry, I know the functions and setup, but we have a development team responsible for that specific area. As production support, we usually do not handle these configuration-related tasks, but I am aware of the features. If I were to configure Splunk AppDynamics myself according to the requirements, I can manage some special cases, but I'm not highly proficient in that part.

For the monitoring capabilities in hybrid and on-prem environments, my experience is that it is hybrid only, as all our applications are based on Azure. Nowadays, every application primarily operates in the cloud, with most servers and infrastructure services utilizing Azure. All the services we use in Splunk AppDynamics are Azure-based.

Regarding transaction monitoring, you get all the details in one place. If anything related to payments is stuck somewhere, within this monitoring tool we can identify which transaction is handed off or not, whether it is payment sent outside or coming back to settlement, allowing us to monitor it easily.

The AI-powered anomaly detection and root cause analysis for diagnosing issues was enabled in my system about six months ago, which eliminates the need to worry about locating errors. You only need to provide the exact statement for the error, and AI will identify the log information for you, showing where to go to find the log. With this AI functionality, it becomes easy to analyze the path of the error. We manage eight hosts, and prior to this AI being enabled, we had to check every host repeatedly. Now, AI tells you which host has the error, simplifying issue resolution.

I provide an overall solution rating of nine out of ten for Splunk AppDynamics, as improvements are always needed. Sometimes, while fetching details, Splunk AppDynamics provides answers within a minute, but it can occasionally take seven or eight minutes, which can be problematic when time is limited.

As a customer using Splunk AppDynamics at UBS Bank, I provide production support for seven payment-related applications, including e-banking, e-trader, and core banking among others. All of these applications are monitored through Splunk AppDynamics. The impressive part is that with a single click, connecting directly to the application dashboard is possible, allowing for streamlined monitoring without manual checks of each application.

I work for a supply chain SaaS organization, and the company is a global supply chain SaaS company that provides supply chain management solutions for global enterprise customers.

For handling enterprise-class customers, we definitely need an enterprise-class product rather than an open-source observability or log management solution. That is why we picked Splunk AppDynamics as our strategic observability and log management solution, and the deployment was completed in a couple of weeks with the help of a third-party vendor.

Log management is the primary purpose for which Splunk AppDynamics is used.

We use Splunk AppDynamics' data collection feature, and using the OpenTelemetry standards, we were able to integrate with our existing set of systems for log management, metrics, traces, and everything that is part of the observability solution offering.

We sell our application management solutions, and the application's digital user experience in Splunk AppDynamics is really good for our global customers. When an external customer is impacted due to application slowness, my support team or my SRE team can go to Splunk AppDynamics portal where we can drill down into the problems, the SLAs, and the response times using this digital experience feature.

For infrastructure monitoring, we are not using Splunk AppDynamics, but for application monitoring, we are using it. The performance is really good and the product features are really good. We have more than 100-plus applications being monitored using Splunk AppDynamics, and for application performance monitoring, the product features are really good.

The team is still evaluating AI-related functionalities in Splunk AppDynamics, but from what I understand from the application owners, they are able to drill down into the application performance impacts during the incidents and they are able to proactively fix the incidents before application portal performance bottlenecks happen.

Splunk AppDynamics did assist me with detecting and protecting against vulnerabilities. It detects the critical vulnerabilities and the legacy things in the larger infrastructure, and it is able to address the critical vulnerabilities in the legacy systems. In that, the product was really useful.

Splunk AppDynamics did help improve my organization's business resilience by reducing the vulnerabilities and the attack surface.

For Splunk AppDynamics, the major headache is cost, and the pricing options are not very flexible. The contract negotiations or the pricing options for a multi-year commitment, along with the renewal cost options, are not very flexible.

In the long run, it is definitely beneficial for an organization like ours, because as a supply chain SaaS organization, we are onboarding many customers every quarter, so the infrastructure grows at the backend for the SaaS infrastructure. If the pricing is flexible, we are going to buy more licenses or more quantity.

Internal solutions were developed, but not third-party products prior to adopting Splunk AppDynamics.

The deployment process of Splunk AppDynamics was done by the third-party consulting firm called HCL.

The deployment was completed in a couple of weeks with the help of a third-party vendor. The deployment process of Splunk AppDynamics was done by the third-party consulting firm called HCL.

I rate eight out of ten for the support for Splunk, and for Splunk AppDynamics, I would rate approximately nine for the support our team is getting. I would rate Splunk AppDynamics eight out of ten overall.

Hybrid Cloud

Microsoft Azure

I use Splunk AppDynamics as our monitoring tool, and it has been effectively used in the last five years to identify major issues and rectify them without causing a major impact to the website.

Splunk AppDynamics tells us what the top 10 queries are which are actually contributing to the load on the database, and it gives us the view of what exactly the query does, whether it uses more DB CPU or is contributing to the roll-up contention on the database. These details provide great insights, making it one of the good features from Splunk AppDynamics.

When it comes to the front end with my Node.js and React.js applications, it doesn't capture much of the details. The improvements I made were mainly around the Java agent side in our app layer, but it was lacking detailed information on the front-end layer. This is a disadvantage, and it could be improved from Splunk AppDynamics' perspective.

I have been working with this solution for the last five years.

It has a cost associated with it, but it is scalable only from a scalability perspective. It is scalable.

I have two different types of technologies used in my project. One of the projects was using a different monitoring tool called Dynatrace, a major competitor for Splunk AppDynamics. Discussions were going on whether I wanted to replace Splunk AppDynamics with Dynatrace, and a decision was made to replace Dynatrace with Splunk AppDynamics because of the capability it has with custom metrics and Java agents. However, discussions are now ongoing about potentially replacing Splunk AppDynamics with Dynatrace. I am using these two major tools in my ecosystem: Splunk AppDynamics and Dynatrace.

I monitor all the business transactions such as basket and add to basket via Splunk AppDynamics. I have set up and diagnosed those transactions.

For the others, they get captured as part of the catch-all transaction itself. In case I need them to be investigated, I use filters to identify the transaction specific to the particular BT.

I have not used auto-discovery as a tool such as analytics and the tracing, trace component, and diagnostic traces much. However, I use historical data to understand where exactly the issue is and try to rectify it.

I have not used the anomaly detection and root cause features.

I have not used troubleshooting as a feature.

Regarding Digital Experience Monitoring, I will lose the limit, causing licensing issues. I identified what pages and applications I don't want to monitor and removed them to cope with licensing. Going beyond the license means paying additionally.

I was not using the Secure Application feature.

Currently, I am not using an on-premises environment, so I cannot comment more on the on-premises side of things as I am using a cloud-based application in all areas.

My overall rating for Splunk AppDynamics is 9 out of 10.

Public Cloud

Other

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.

Dynatrace has multiple functions compared to Splunk AppDynamics, so Splunk AppDynamics should add those functions, which are not available as of now. Dynatrace has a universal agent that collects all information related to their CI, and if one CI has multiple languages, then there is no need to instrument multiple agents. 

However, Splunk AppDynamics requires multiple agents; if I have one server with multiple applications in different languages, then I need to instrument different agents for each application. 

Splunk AppDynamics should work with Dynatrace with one single universal agent that works with all application languages, eliminating the need for multiple implementations.

Regarding stability, it is a very nice and good tool. There are no issues or bugs with the 20.4 version; it is very stable with no functionality or operational issues. I would give it ten out of ten.

The support team for Splunk AppDynamics is very helpful, and they help us resolve any issues raised by our team relating to operations, application instrumentation, or any other issues. I would give them a nine out of ten.

Positive

The new version is very straightforward. I would give it a ten out of nine, and there are no issues related to deployment; it is very easy and straightforward to deploy.

There are multiple benefits related to the APM market, but we experience benefits related to application performance only. According to errors, exceptions, and code-level details related to their application performance on a daily basis, the application development team tries to help with Splunk AppDynamics to reduce errors and exceptions, which helps the end users get application availability and feel more confident.

I rate Splunk AppDynamics 10 out of 10.

On-premises

Other

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 best feature of about Splunk AppDynamics is its interface, which allows me to see the full transaction, exactly what is happening, from where it starts to where the call is going, all the services involved in a call, and exactly the time it took from each node to each node along with the network delays. It pretty much provides everything a performance tester would need to do profiling of their results.

Splunk AppDynamics has enormous capabilities that allow me to see the memory and CPU usage, along with the garbage collections. In the case of performance issues, it allows me to dig through the transactions and find out what exactly the issue was to alert the architects and developers to address that issue. I am very happy with Splunk AppDynamics.

I don't really use AI-powered anomaly detection and root cause analysis for diagnosing performance issues because it makes many mistakes in my case, due to the nature of my work.  I prefer to do it manually and be aware of what is going on, rather than relying on that.

If it could have a sub-tool for monitoring Apache Kafka lag, it would save me even more time. There are ways to do it now, but a direct way would be faster and better. 

It would be much better if there were a way to search for specific transactions, similar to how Splunk allows, which aids in filtering transactions that show a huge increase in time.

I have been using Splunk AppDynamics since 2019.

In the early years, we had a couple of issues. It is more stable now. I don't see any of those issues anymore. There are no downtimes. I would rate the stability of Splunk AppDynamics as a nine out of ten.

I would rate the scalability of Splunk AppDynamics as a nine out of ten. A few features could be added to reach a perfect score of ten.

Our environment includes multiple locations and multiple departments. In my company, there are many users working with Splunk AppDynamics.

I haven't worked with them directly. I remember the developers contacted them once, and they received answers within one or two days. I would rate their technical support as good.

Positive

I have experience with other solutions, but I see Splunk AppDynamics as a top-tier option, with the rest I've worked with falling far below it.

Splunk AppDynamics stands out in the freedom it provides you to visualize everything. You can pretty much monitor anything that comes to your mind. It doesn't specify a way or how to do it. That's very important for me because it makes my job easier. I can configure it or work in thousands of ways. Along with Splunk, you can even see the logs in-depth. You can see exactly what happened at which transaction and where. Other tools don't provide this much depth or this much freedom to do things you want.

Developers did the deployment, not me. As far as I remember, it was done in less than two days. 

The company I work for now has an enterprise solution.

It does require maintenance, but it's not my job. That's other department's responsibility.

We have seen a return on investment from Splunk AppDynamics. To understand the magnitude of it, without it five people would be needed to do the analysis that Splunk AppDynamics enables me to do. Splunk AppDynamics has definitely saved me many hours per week, approximately 50% of the time.

I would recommend Splunk AppDynamics to other users because it has helped me in many ways. It is a very stable and solid tool. It never has false results. I have seen other tools producing wrong results. That's not the case with Splunk AppDynamics. It either works and provides solid results, or it doesn't work and requires maintenance, which is a very important distinction. It has a very nice graphical user interface. It allows someone to interpret things easily. It provides freedom to the user to use it as they want. These are the reasons I would recommend it.

I would rate Splunk AppDynamics a ten out of ten.

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. 

With Splunk AppDynamics, the database part is interesting. 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. For example, the baseline of all metrics in the Splunk AppDynamics database is very interesting. It can send alarms or alerts when the database baseline is not correct.

The effectiveness of the Splunk AppDynamics auto-discovery and mapping is similar. It's maybe a little better than APM from Broadcom. However, it's not the best. Users need to modify or configure many things to get good information from discovery. It's good, yet there is something to improve.

Business transaction monitoring is the more interesting part of Splunk AppDynamics since it has automatic discovery of business transactions and many different kinds. For example, for web services or different kinds of components, such as in Java. Users can configure business sections in their environment, and it's possible for customers to configure different sources for the name of the class, the name of the method, or the name of the web service, which is very interesting.

I work with the AI-powered anomaly detection and root cause analysis for troubleshooting. Users can see the error and the message with the error on the dashboard, and they can see exactly what error they are encountering.

The user experience is good. Its impact is very high. It's crucial to be easy to manage for the customer's user experience.

The discovery is acceptable, however, users need to configure many things if they want good discovery. These points are candidates for improvement.

A good integration with the CMDB would be beneficial, so users can see a good view of the final services automatically. A good integration with Splunk would be very interesting, as Splunk is a good product for logs, and that part is currently missing in Splunk AppDynamics. If Cisco can achieve a solid integrated solution, it would be very beneficial.

I have used Splunk only for the security part, not with the APM part - only with the security and management of logs. I have used Splunk AppDynamics for approximately five years.

The solution is stable.

The solution is scalable.

We have had a good experience with Splunk AppDynamics compared to APM from Broadcom. AppDynamics if much more helpful.

Support is generally okay, and the support is knowledgeable. 

Positive

We have experience with another solution, with performance, with application performance, with infrastructure, alongside the other product we are working with.

It's very different. The most important aspect is that the discovery of Splunk AppDynamics is better than APM from Broadcom, along with the dashboard and many other features.

It's very complex regarding pricing, setup costs, and licensing of Splunk AppDynamics. Normally, when we have to do a quote for a customer, we talk with Cisco, and it is very complex. For me, it is more complex than APM from Broadcom, which is easier. Cisco being complex depends on the part of the solution, the agent, and many things.

The solution is better in on-premises environments.

Splunk is only SaaS, and in two years, or when these solutions are integrated, maybe it will be a better SaaS solution. Right now, for on-premises environments, it's the best.

There is maintenance needed, and it's important to do the maintenance work. We have to do a lot of things to maintain it properly. It's not difficult. However, you do need to do a bit of work - more so than APM Broadcom.

Ten years ago, it was good, however, now it's complex in Cisco. We tried to integrate Splunk with Splunk AppDynamics, and maybe in the future, it will be a good solution. Right now, it's two separate solutions, and it's not a good integration.

Splunk AppDynamics' infrastructure monitoring is satisfactory. Users have a main dashboard with all information. If there is a problem with memory, CPU, or something else in a server, users get a red alert, and they can click on that component to see the specific metric related to that CPU, memory, or network problem, and the correlation is very good.

It optimizes the user experience for customers.

My experience is more from Java and .NET applications. I don't have security skills, however, customers find it acceptable to see this information in the global context regarding their applications.

It depends on the integration with Splunk that I mentioned before. I prefer to wait to see what happens with that, but Splunk AppDynamics is a very good solution, and I believe that integrating Splunk will yield excellent results.

On a scale of one to ten, I'd rate it a seven.

On-premises

Other

Our main use cases for Splunk AppDynamics involve monitoring our web stores.

Splunk AppDynamics has helped improve my organization's business resilience.

The features of Splunk AppDynamics that I prefer most are the monitoring aspect, making sure we can drill down and find problems. Splunk AppDynamics features benefit our organization by being effective; we use it consistently, and it is definitely utilized.

My impressions of Splunk AppDynamics' ability to predict, identify, and solve problems in real-time are that we've been using synthetic monitoring, and that's been really helpful, allowing us to see issues before customers experience them.

AppDynamics helped improve our organization's business resilience.

Splunk AppDynamics can be improved. I install it frequently and sometimes when they fix something, they break something else, so better QA is needed to ensure the quality of their fixes. There aren't any additional features that should be included in the next release because everything they're discussing at the conference is what we want to make the software better, so I appreciate that aspect of what they're doing.

I have been using Splunk AppDynamics for two years.

I assess the stability and reliability of Splunk AppDynamics as generally reliable, and we don't have issues accessing it, being SaaS.

I assess how Splunk AppDynamics scales with the growing needs of my organization as good, since we are growing and adding more servers. I have not expanded usage currently because we're in a freeze, and we don't try to update anything. Before the freeze, I did expand usage. The expansion process was pretty smooth.

I would evaluate customer service and technical support with Splunk AppDynamics as generally good since they usually respond to us within 24 hours.

Positive

The initial deployment wasn't so good. Smart agents didn't work. Trying to upgrade didn't work. On Linux, there are a lot of locking issues. You gotta make sure that libraries aren't getting updated. So there's always some type of conflict. When we do get to work, it works great, however, you have to go through all these steps before you can make it work properly. We spend hours, days trying to figure out what's wrong with it. Then, we contact support and go back and forth.

I have not seen ROI with Splunk AppDynamics from my level.

My experience with pricing, setup costs, and licensing for Splunk AppDynamics is that it's extremely expensive, and we completed a three-year deal for Splunk and for AppDynamics, which costs millions of dollars.

My impression of Splunk AppDynamics' AI-powered anomaly detection and root cause analysis in diagnosing performance issues is that we don't have the latest versions to get all that functionality, however, we're working on it, and we have an issue with smart agents.

I assess Splunk AppDynamics' infrastructure monitoring as doing the job in correlating infrastructure and application performance, and it has been around for a long time.

My advice to other organizations considering Splunk AppDynamics is that they demonstrate how everything's interconnected immediately, but there's substantial customization required around your own business, and out of the box, you need to configure it to make it work better for you. We spent significant money on professional services to help us accomplish that.

On a scale of one to ten, I would rate Splunk AppDynamics overall a nine.

The root cause analysis they have is exceptional. It is a satisfying product, especially the smart agent collectors, which help us significantly. 

The real user monitoring and digital experience monitoring effectively track actual user experience with the applications, including page loading, interaction time for both desktop and mobile applications.

AppDynamics' AI-powered anomaly detection and root cause analysis in diagnosing performance issues is good. It doesn't have many false positives.

They have one aspect that needs improvement. They should combine the cloud and EPM on-premises together and provide a unified single pane of glass for all their modules because they currently have different modules for infrastructure monitoring. My expectation is to unify the management console into one single pane of glass console to manage everything and have all visibility from one place.

We have completed three years with Splunk AppDynamics.

It is good.

The scalability is fine. Many people are using it. We are a system integration company selling this to clients. Our clients are medium to large-sized businesses, typically ranging from 800 to 8,000 users.

I would rate them an eight out of ten.

Positive

It's a bit complex; it's not exactly easy. It's moderate in difficulty. You need some experience to implement it.

It is a good solution. It has strong capabilities. You cannot compare Splunk AppDynamics with others. If you want quality, you need to pay, so the cost is justified.

I would recommend it for financial institutions and banks, as well as any companies that rely heavily on online applications, like e-commerce service providers.

I would rate Splunk AppDynamics an eight out of ten.

Public Cloud

Microsoft Azure

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. 

The metrics browser is very useful, and the deep dive feature is very useful for us. 

Product-wise, everything is good, but the main concern is the extensions and their documentation, particularly for the installation of Azure app services. It is lacking some documentation, which is why we are always with the AppDynamics team for support to get the details.

Additionally, whenever they upgrade or add new features, we do not get notifications, which makes it very hard for us to find out new information. If they could fix this, it would be helpful, and our satisfaction score would increase.

We have been using Splunk AppDynamics for almost three years.

We are using the cloud version only and not an on-premises installation. I am not sure what to expect on the scalability front, but it is useful for us. We have tried it with a maximum of 500 concurrent users, and it provided all the required information.

Initially, we had some hiccups getting technical support. After some time, we got a contact, an account manager, to work directly with for technical support. He immediately finds a resource and assigns it to us.

Positive

We haven't done that exercise. We are working on a mix of applications, such as SaaS, AWS-hosted, Azure, and on-premises applications. It's very hard to find ROI because we are currently focused only on the on-premises applications. In a year, we work on about 20 projects, but we get only two or three projects using Splunk AppDynamics. For the others, because they are vendor-hosted, we don't utilize it. We are still trying it, and maybe once we develop that capability, we'll start finding ROI. Currently, we are not performing any exercise on calculating ROI.

We find its pricing reasonable and competitive. After it was acquired by Cisco, we found it acceptable.

I would rate Splunk AppDynamics an eight out of ten.

I am currently supporting Blue Yonder, where I implemented the Splunk AppDynamics solution for EY, Ernst & Young, and now I'm working with international companies, as you may be aware of Blue Yonder. I'm implementing Splunk AppDynamics for Blue Yonder, which has a variety of logistics and supply chain management applications to monitor, serving around 500 plus clients.

Predominantly, for this current project, we are using Application Performance Monitoring in Splunk AppDynamics, mainly for the Java instrumentations, as our application is completely based on Java, which helps to identify business transactions, bottlenecks, and also monitor database performance using custom queries.

I find the anomaly detection feature in Splunk AppDynamics quite good, as it was introduced about a year back, and we had enabled it.

Infrastructure monitoring in Splunk AppDynamics is really helping as it allows us to understand overall application performance and any bottlenecks, especially when we implement the machine agent alongside Application Performance Monitoring.

The main benefits from Splunk AppDynamics for my end users, mainly the application team, are that it helps identify bottlenecks proactively and allows for configuration of proper health rules to address issues before they affect customers.

I see that the main challenge with Splunk AppDynamics is the management of multiple agents, as installing several agents on a server is a significant hurdle we still face.

Functionality-wise, I would like to see more cognitive solutions in Splunk AppDynamics, ideally with a single agent that can implement policies and provide predictive insights regarding application performance degradation during peak times.

I have been working with Splunk AppDynamics for almost five to six years.

I rate the stability of Splunk AppDynamics an eight, as I have not faced many stability issues with the product.

Regarding scalability, I would also rate it an eight, as I have not encountered significant performance issues, especially being in a stable SaaS environment.

With our premium support contract for Splunk AppDynamics, we are very satisfied, receiving consistent support including bi-weekly calls with customer success managers and product specialists.

Currently, people are leaning toward Dynatrace, possibly due to its AI capabilities such as the Davis feature, which offer a single agent concept that is easier to implement and maintain.

For Splunk AppDynamics, the initial setup process I've encountered has been simple since I only increased the scope of what was already established four years ago, and while there is a challenge with multiple agent solutions, the product is generally beneficial.

We purchase Splunk AppDynamics through our vendor, HCL Technologies, as they handle all sales instead of direct from the vendor.

In my opinion, the main competitor to Splunk AppDynamics in the market is Dynatrace.

Public Cloud

Amazon Web Services (AWS)