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. 

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. 

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.

The main use case for Splunk AppDynamics will be legacy application observability.

Splunk AppDynamics is useful for helping my clients improve business resilience. If you combine Splunk and AppDynamics, the features missing in AppDynamics can be supplemented by Splunk. By streaming telemetry from AppDynamics into the Splunk data lake, you can apply missing AI analysis and provide better service management and predictive analysis, which helps reduce the meantime to resolution.

Combining Splunk and AppDynamics allows for improved features and predictive analysis by streaming telemetry from AppDynamics to Splunk.

None of the features or functions in AppDynamics are very useful or unique nowadays. AppDynamics has stopped in time at least five years ago, so there's nothing unique from Splunk or from AppDynamics nowadays.

The OpenTelemetry part of AppDynamics is not good for a specific reason: AppDynamics is not a native OpenTelemetry. They have collectors that convert OpenTelemetry to be indexed, causing performance problems. Most of the instances of AppDynamics experience outages, especially the larger ones, and I am not happy with that since it cannot cope with current trends.

It is not a question of lacking key functions in AppDynamics; they have all the functions, but the back-end architecture needs a complete update. AppDynamics has existed for many years, and a drastic restructuring is necessary. I have suggested to Cisco or Splunk that they should merge AppDynamics functionalities with Splunk Observability to simplify things.

My thoughts about infrastructure monitoring and the correlation with application performance in AppDynamics is that it is pretty basic with their health rules. It involves human capability to understand the impact on applications, but when it comes to proper observability and root cause analysis, it is non-existent in AppDynamics.

I have been working with AppDynamics for ten years.

For stability in Splunk AppDynamics, I would rate it as a six.

Regarding scalability, I would rate it as a five.

I would rate Splunk's vendor support as an eight. While some staff are not as helpful, there are many who are good and provide a lot of help.

Positive

I currently still work with Splunk, so I have not moved to another vendor.

The setup process depends on whether it is a SaaS or on-premises solution. For SaaS, which is common, I would say it has mid-difficulty since Splunk does most of the setup, but issues arise with needing multiple agents for each technology, making automation challenging.

Regarding pricing for AppDynamics, I would rate it as high cost, but this is primarily because the ROI is very low today rather than the license costs. I work for an MSP and have a massive discount, yet I see better ROI in competitors like Dynatrace, where the benefits to customers are higher.

In my opinion, the main competitors in the market for Splunk AppDynamics are Dynatrace and DataDog, though I do not even consider them serious competitors anymore.

In my opinion, AppDynamics does not have any AI capabilities at all. Anomaly detection is based on an algorithm and is not AI; it is machine learning, which are two different things. They do provide basic anomaly detection based on metrics, not logs, but there is no large language model implemented in LogicMonitor.

My feedback about Splunk AppDynamics Digital Experience Monitoring is that it is adequate and follows standard Digital Experience Monitoring practices. They allow you to combine data from ThousandEyes into the Digital Experience Monitoring or user monitoring, which is a useful feature that helps with root cause analysis when there is an issue affecting user experience. However, there are no enhanced features; it is pretty much out of the box.

In my opinion, the Security Application feature in AppDynamics is quite good. The DevSecOps section is ahead of their main competitors, but not for long. They offered very good code-level monitoring when they launched, but they have not evolved the product, and competitors like Dynatrace and DataDog are catching up.

My final recommendation for Splunk AppDynamics is to decommission it and merge it with Splunk Observability. I would give it a rating of six out of ten. I would not improve anything in AppDynamics; instead, I would decommission it and prefer the functionalities to be merged with Splunk Observability.

I use Splunk AppDynamics for monitoring the infrastructure and the applications, their health and performance, and any bottlenecks on memory or disk, as we have defined many KPIs. There are specific use cases where we need to send data out very fast, and to ensure we are not breaching the SLA, we monitor closely, especially if we need to tune something on our application side. It is primarily for infrastructure monitoring and application monitoring.

The best features of Splunk AppDynamics that I appreciate include the ability to drill down to a specific transaction, which is very useful for analyzing situations. For example, we might have 10,000 transactions in one hour, but if there is only one transaction taking five seconds while all others are processed within nanoseconds, we can drill down into that transaction and see the details, which is very useful for us.

I appreciate the speed and the details that Splunk AppDynamics provides, and the visualization is also good for anybody who is not technical enough to understand where the data is coming from, whether it is a transaction on an API, a web service request, or JMS. Splunk AppDynamics has very good visualization that allows a non-technical person to grasp some basics, such as understanding where we are receiving something from and how it flows.

My thoughts on the AI-powered anomaly detection and root cause analysis in Splunk AppDynamics are that in the first two or three years, it was not very great, possibly because it lacked sufficient data. However, now it suggests possible reasons since it has enough data to identify potential issues, so we do not have to look everywhere. Based on the input we receive from the agent or dashboard, we focus on selected areas, saving us time during investigations and reducing the time from four hours to just one hour.

The time saved is significant as we have gone from four hours to one hour, which means we are saving a lot of time. If there is an issue requiring root cause analysis, we typically look into 10 areas, but Splunk AppDynamics helps us focus on about three or four areas, where we find 95% of the issues based on its suggestions, making it an effective time-saver.

Splunk AppDynamics has indeed helped improve our business resilience by allowing us to carry out proactive maintenance and identifying problems beforehand. We monitor application heap memory thresholds and take corrective actions before any crashes occur, which definitely indicates its effectiveness.

If I consider what can be improved in Splunk AppDynamics, I would point out that it could enhance its reporting capabilities, as it remains very technical. Some business users struggle to create their own dashboards or reports because they are not technical and do not want to dive into the complexities, so making it more user-friendly in the manner of Tableau would be beneficial.

My experience with Splunk AppDynamics is approximately five years.

In comparing Splunk AppDynamics with other vendors, I find that for conjunction monitoring of infrastructure and applications, it is one of the best. However, for pure infrastructure monitoring, tools such as Dynatrace and BMC might be better suited, so the choice depends on your specific use case.

Regarding pricing, I reiterate that I think it is right on target and it is cheaper than Dynatrace.

Regarding how Splunk AppDynamics' digital experience monitoring affects user experience, I think it is similar to other tools such as Dynatrace. From a user experience perspective, all of these applications, including BMC Remedy, have essentially the same layout, so I would not say it has any standout advantage in user experience.

When I assess the infrastructure monitoring of Splunk AppDynamics in correlating infrastructure and application performance, I find it to be better compared to tools such as Dynatrace or BMC Remedy. Splunk AppDynamics excels in monitoring both infrastructure and applications together, offering better insights than when using just infrastructure monitoring tools.

I would recommend Splunk AppDynamics, but my advice is that it depends on what you are trying to monitor. It is best for monitoring both infrastructure and applications together, but if you are monitoring just infrastructure, it might not be right for you, as it is situated in a competitive space alongside tools such as Dynatrace and BMC Patrol. I would rate this product as an 8 out of 10.

We use Splunk AppDynamics for infrastructure, application, and Kubernetes monitoring, as well as private synthetic agents. We use it for all purposes, including as an extension for log monitoring and every extension. We develop any custom extensions as needed.

At present, I am actively working on a private synthetic agent in Splunk AppDynamics, which we have deployed internally in our IKP platform. I am currently working with that by developing Python Selenium scripting.

I have experience with Splunk AppDynamics' Digital Experience Monitoring, including end-user monitoring. For the functionality part in Splunk AppDynamics, I am comfortable with it.

I find all functions valuable in Splunk AppDynamics because I am from the AppDynamics team in my current company. We help with user queries, and the value depends on the use cases, which might be different for each user.

My impression of Splunk AppDynamics' AI-powered anomaly detection is that it functions very well. The anomaly detection gives the exact root cause of what is happening on our server, and for analytics, for every application, we mostly try to configure the analytics to visualize all the things.

Splunk AppDynamics is useful for me and everything is working out fine. Previously, with log monitoring, I might have been a bit unsatisfied with that. As it is integrated with Splunk, that is also very good.

Splunk AppDynamics gives all the metrics that report to AppDynamics, and they work very well and provide precise information from the server. For application performance, it also gives all the business transactions very efficiently. If there are any other things, we can configure them by an extension or manually.

For now, all secure application features in Splunk AppDynamics are good with me. But in the future, I need to go through all of that because while I have experience, it majorly depends on the use cases. I also need to acquire more knowledge on some of the concepts of AppDynamics.

Splunk AppDynamics is very efficient in all those areas. Compared to the cost, it is also very cost-efficient, because that is the main thing for every organization. For all the things concerning metrics, it is also very good for now.

I am somewhat aware of the data collection features in Splunk AppDynamics, but for now, I have not worked on it.

For now, Splunk AppDynamics is a very efficient tool. However, we have a slight complexity where for infrastructure we have to go to one agent, for the database we have to go to one agent, and for the application we go to another agent. For applications also, depending on the type and nature of the application, we have to go to different agents. Different agents mean we need to install different agents. This is something I find a bit more complex.

I have been working with Splunk AppDynamics for two years.

I would rate the stability of Splunk AppDynamics a nine or ten because it gives efficient monitoring.

I would rate the scalability in Splunk AppDynamics an eight.

Before working with Splunk AppDynamics, I was working with Dynatrace and DataDog.

I have been working with Splunk AppDynamics for the past two years. Before, I was working with Dynatrace and DataDog. When I came to Splunk AppDynamics, I found it a bit more complex because for everything, we have to go to different agents. I found this part a bit difficult, but since I have been working with it for two years, I am becoming habituated to it.

With DataDog, the UI is very simple. If you compare Splunk AppDynamics and DataDog, the UI accessibility and all the things are very simple there. There will be only one agent present where we deploy all the things. The configuration of alerting policies, which you configure in Splunk AppDynamics, are also very easy there.

I can confirm that I am still working with Splunk AppDynamics.

I am using Splunk because it might be different from Cisco to Splunk. For now, everything is good with me. I think Splunk AppDynamics is more evolved, so for now, all things are good with me. My overall rating for this review is nine out of ten.

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.

A main use case for Splunk AppDynamics is monitoring the applications in production environment. We are doing infrastructure monitoring and application monitoring.

For all the applications, we monitor the infrastructure such as CPU, disk, and memory. If there are any issues with CPU, memory, or processes, we send alerts to the teams. Similarly, we do application monitoring for JVM and server availability.

We are using Splunk AppDynamics for troubleshooting predominantly, and sometimes for capacity planning as well.

The best feature about Splunk AppDynamics are the Business Transactions. It automatically detects and captures them, which helps most of the application teams.

Whatever the important business transactions are, it automatically captures them and their performance as well. If there are any performance issues, business transactions will help point out exactly where the performance has been degraded. This helps the development team to troubleshoot and rectify if there are any modifications required in their code.

Splunk AppDynamics monitoring is helping our organization. Because of this tool, we have reactive monitoring. Whenever there are any issues, the application will get the ServiceNow ticket. This is the policy in our organization. If the threshold criteria is exceeded, it creates a ticket and assigns it to the application team. The application team investigates that issue, and in that way, we avoid downtime. Apart from that, if there are any application performance issues, with the help of business transactions or memory leak functionality, the development team will be able to drill down that issue and fix it faster than the traditional way.

We have seen application availability increase. There is a twenty-five percent reduction of the application downtime.

With Splunk AppDynamics mapping, it captures the business transactions and provides the feature to add business transactions or eliminate those which are not necessary. This auto-mapping helps most of the applications.

With the help of infrastructure monitoring in Splunk AppDynamics, server availability is one of the key features. It captures the memory, CPU, and disk. These are helping my organization to keep all the applications up and running with minimal downtime.

We are looking for some more common extensions and custom extensions. Specifically, we are doing log monitoring, URL monitoring, and port monitoring. We are looking for cloud monitoring if there are any features available in Splunk AppDynamics.

Splunk AppDynamics can be improved specifically by providing the log monitoring feature that is currently not available, centralized log monitoring. I know that is available in Splunk. Apart from that, we are seeking to address a couple of issues in Splunk AppDynamics. Specifically, machine agents are not reporting, or we have to restart our machine agents. Another issue is with disk utilization. For disk utilization, it will automatically detect the mount path, but we have seen for many mount paths, even though they are mounted, the data is not reported in Splunk AppDynamics. If the Splunk AppDynamics tech team fixes these issues, that is going to help significantly. Additionally, there is one more feature regarding how we can do cloud monitoring with the help of Splunk AppDynamics. Regarding the market trending with AI, how will Splunk AppDynamics help with artificial intelligence?

In the technology stack, I believe Python is going to be heavily used in AI applications. I'm not certain about this. We currently monitor Python, but it is not as extensive as Java monitoring. If Splunk AppDynamics provides more information on Python monitoring or artificial intelligence application monitoring, that will be helpful.

Customer support takes time. Whenever we face any issues, we have to open the vendor case and then there will be back and forth happening. I can see there is an opportunity to improve the customer support in Splunk AppDynamics.

I have been using Splunk AppDynamics for the last four years.

We have not seen any issues with Splunk AppDynamics. It is stable. We haven't seen any outages.

We have not seen any issues with scalability. We were able to scale up as the number of applications increased.

Customer support takes time. Whenever we face any issues, we have to open the vendor case and then there will be back and forth happening. I can see there is an opportunity to improve the customer support in Splunk AppDynamics.

Positive

Earlier we were using some other monitoring tool, and troubleshooting in that monitoring tool was difficult. We switched to Splunk AppDynamics because of the business transaction feature specifically and other customized extensions available.

Before choosing Splunk AppDynamics, we evaluated some other tools as well. Specifically, we tried our hands with the Tivoli monitoring tool. We are still using OpenText as well, which is also a monitoring tool. We have used some other tools as well, but we chose Splunk AppDynamics because of its user-friendly UI and because it is easy to understand.

Splunk AppDynamics is user-friendly and it's easy to monitor applications and troubleshoot. This helps the entire organization.

It requires minimal training to get onboarded for the application team as well as the support team.

Recently we are exploring how Splunk AppDynamics can be integrated with OpenTelemetry, but we are in a very initial stage.

Depending on the organization's requirement, we will definitely recommend Splunk AppDynamics because of its features, specifically all the custom extensions, and to maintain the application uptime. Splunk AppDynamics will help. It requires minimal training to get onboarded for the application team as well as the support team.

I think with the current era, we can see Splunk AppDynamics being a costlier tool. Most of our clients have shown an inclination toward open source tools, such as DataDog. Many applications and many organizations are using Grafana, and there are other tools available, so they are exploring that possibility because of the pricing.

There were a few issues that we have noticed with Splunk AppDynamics. Data is not reporting, and custom extensions are not readily available. That is why I have chosen seven out of ten.

This metric is not currently available on top of my head.

I believe you have covered all the points, and I am satisfied. My overall review rating for Splunk AppDynamics is seven out of ten.

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.

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.