Splunk AppDynamics Reviews

In the financial sector, banks primarily use Splunk AppDynamics for monitoring their digital apps, such as mobile banking and internet banking applications. These client-facing applications are the primary usage of this tool.

The main use case with Splunk AppDynamics is infrastructure monitoring. End user monitoring is also considered, but infrastructure is the main component.

The main benefit is that for application performance, sometimes banks face issues related to databases or performance problems. Splunk AppDynamics helps them identify the root cause. Sometimes external calls going to services such as NADRA in Pakistan or other verification services face delays in getting responses from their side. These types of issues are easily identified, and they can pinpoint where the problem lies.

AI-based features were checked in Splunk AppDynamics. The feature is helpful, but unfortunately, the financial sector is not using the full feature cloud version. Mostly deployment is on-premises.

End-user monitoring (EUM) is another area that customers are normally interested in, and it is very helpful.

Saving time is definitely the main point with Splunk AppDynamics for quickly resolving problems. Whenever they are facing an issue, they quickly identify the root cause and can proceed with fixing it. Sometimes if performance issues arise, they can pinpoint where the problem is. These things help with better performance and customer experience is actually better. This definitely helps them to get more financial benefits. If the users and customers are comfortable and happy with the banking apps, they are more loyal to that particular bank. Everyone now, almost all banks, are looking for APM tools. Initially, three or four years back, people were not considering this tool as one of the essential components for their infrastructure, but now everyone is looking for these types of tools.

In terms of improvement potential for Splunk AppDynamics, there is one point that competitors are exploiting, which is the smart agent type of thing. Dynatrace is saying they have a single agent for all types of applications, which is easy to deploy. Splunk AppDynamics still requires different agents for different applications. Splunk AppDynamics has added the feature of the smart agent, but it is not very effective, as my engineers informed. They still need different agents and community-based agents to manage the different applications. Another challenge we are facing is that for some legacy applications, such as those customized applications developed by customers or their local software partners that are built on C++ or other languages, we face issues in monitoring these applications because we don't have any agent. In some cases, we lose deals just because we are not able to monitor the application developed in C++. These types of support should be there in Splunk AppDynamics.

From a functionality standpoint, Splunk AppDynamics is good. There may be some improvements required, especially for dashboarding. People are also using Elastic or Grafana for dashboarding, and they find their dashboarding more appropriate in displaying information in reporting or dashboarding. Splunk AppDynamics can focus on enhancing reporting and dashboarding. They could enhance or integrate with Grafana or any other reporting tools. One customer required historical reporting the way other network monitoring tools provide it in PDF format. They have a historical report that they can generate and present to their management. However, in Splunk AppDynamics, the approach is different. If someone wants historical data, the dashboard is dynamic, so they can identify the time slot, and it is the same dashboard that they got. If they go back to historical data, the same dashboard generates the report, taking a snapshot of that dashboard. There is no detailed reporting in PDF or Excel format as other tools provide. This is another area that requires improvement. The reporting should be detailed in PDF format; right now it is the same interface that the customer is getting on the dashboard.

I have been working with Splunk AppDynamics for three to four years.

I would rate the stability of Splunk AppDynamics as an 8.

For the ability to scale and expand with Splunk AppDynamics, I would rate it 7 or 8. Sometimes customers face resource issues because they have to enhance their infrastructure as local logs and local storage fill up quickly, so they have to clean up.

Technical support for Splunk AppDynamics is fine, so I rate it 10. We are not facing any issues.

Initially, the setup process for Splunk AppDynamics is complex, and teams are facing some challenges in the initial setup. However, now that the team is used to it, it does not look very complex. Splunk AppDynamics can focus on making it smoother.

The main competitors on the market for Splunk AppDynamics are Dynatrace and Elastic.

Still, I think Splunk AppDynamics is better, but slowly and gradually over this last year, I can see that Dynatrace is also gaining penetration in this market. Maybe worldwide, they are also progressing because with every customer now, we are actually facing competition with Dynatrace. Out of four to five customer bases, they are able to get one deal if we are competing in five. Still, we are getting more deals, but they are starting to penetrate into this market.

The features that Splunk AppDynamics is providing are really helpful, but in the Pakistani market especially, it is a costly proposition for the customer. Customers are using third-party tools for security, and Splunk AppDynamics is not very popular here for security.

Splunk AppDynamics allows us to understand the mean time to resolution and decrease it by easily understanding the dependency of the full application flow map. For root cause analysis and other hidden aspects, we can see how code quality performs. SQL queries can be easily evaluated for quality, and when code quality is not good, we can identify slowness in specific classes and methods. We can see which parts of methods and SQL queries are facing slowness issues. After that, we can develop and change code, modify database queries, and easily see in the product environment without needing to debug facilities. We can see in real time whether code changes are affecting the system positively or negatively. There are many different advantages, and we can separate proactive and reactive sides.

When we collect different method parameters with the essentials of monitoring APM tools, we can easily combine business and operational development cycles in a single pane. For example, when development teams make process improvements to code to add new features to transactions, we can easily see how this feature affects customer experiences as performance metrics. If we can collect this kind of data, we can also easily combine business and operation metrics. For example, with a loan application from the customer side, such as a bank customer making a loan application over their mobile or internet banking application site, we can easily see how many successful transactions occur in real time from a business perspective, not just from the performance side. If we can collect these metrics, we can combine all performance and business metrics in a single pane, giving customer sites a very different and big picture view.

Splunk AppDynamics works for Java, .NET, .NET Core, Node.js, and PHP applications. We also work with some customers using SecureApp features, and customer feedback has been really valuable for us. From my customers' experience with this feature, the feedback is really positive. In the software development lifecycle, penetration testing or security testing before getting a project into live production environment is a very important process. You have to conduct penetration testing before going live with your project. However, this kind of penetration testing is a bit reactive and offline because you only perform this penetration testing from a synthetic point of view, for example weekly, monthly, or quarterly. With Splunk AppDynamics SecureApp solution, we can easily see our application's vulnerabilities, attacks, and exploits in real time. We can also see any vulnerability, even zero-day attacks, easily after they occur. This is a really cool and differentiating feature, though it is a very new feature in the APM market, almost two years old. Because of that, it is not well-known, but when we demonstrate it to customers in POC or demo sessions, most customers are impressed and want to try it in POC. After POC, some customers want to buy this feature while getting the APM solutions as well.

We can monitor what kind of vulnerabilities exist in the code and can easily show the business risk in the environment by making a business score, not relying on MITRE or CVE codes. The scoring also works from a business perspective. For example, if we have one vulnerability that may be medium severity, our internal scoring mechanism increases the business risk if the application touches databases or other inside applications. If the application is not communicating with other applications, databases, or other sources, the business risk may be lower than the other example because of the application's touching points. This is a really cool feature. We are not only reporting these vulnerabilities, but we are also blocking these attacks in real time. For example, when a Log4j2 vulnerability occurs on the system or any zero-day attacks happen, Splunk AppDynamics easily tags and understands this kind of attacks. If desired, it can easily block the application's attacks from the APM perspective. This is a really game-changer in my opinion.

I think one of the really strongest features of Splunk AppDynamics is the end-user experience monitoring. We have a really differentiated capability over our competitors. We can easily adapt our solution to the customer's application, internet banking solutions, or IoT devices all over the world. For example, when you get a new Volvo from any Volvo shop, that car has a built-in Splunk AppDynamics light agent to track their connected car applications. To give a specific example, Audi, Volvo, and four years ago BMW also use Splunk AppDynamics light agents to monitor IoT devices and connected car applications. Mercedes may have this kind of agreement as well. In summary, we can easily monitor mobile devices, including Android and iOS, browser-based applications, and also IoT devices. For example, in Turkey, I personally use IoT monitoring with my customers. We work with banks, and most customers monitor their ATM devices and POS devices via Splunk AppDynamics agents. I have personally implemented the IoT agent or Splunk AppDynamics agent into ATM devices and POS devices, as well as for some cinema companies' kiosk systems.

I can mention two different things. First, Splunk AppDynamics is mostly compared with the Dynatrace solution because they are a really good solution. They offer on-premises options as well. I know Datadog is another good solution, but it only works with SaaS solutions. New Relic and Grafana are also good solutions, but Splunk AppDynamics and Dynatrace are the only on-premises options in the marketplace. Because of that, I want to compare with Dynatrace. Dynatrace has a OneAgent mechanism, while Splunk AppDynamics has a smart agent mechanism. The idea is quite similar, but when you use the Dynatrace OneAgent solution, because you are giving administrator and root rights, it is a bit easier but unsafe. For Splunk AppDynamics, you do not need to give the agent administrator or root privilege, but because of that, its capabilities are a bit limited. I cannot directly say this is a negative thing because it depends on the perspective. For example, if you really stick to security mechanisms, security teams can say that Dynatrace is easy to install and monitor, but from the security perspective, it is terrible and awful because you are giving full administrator and root privileges to Dynatrace. Splunk AppDynamics could improve their installation process, which would be an incredible thing on Splunk AppDynamics' side.

Second, most products, even Dynatrace, Splunk AppDynamics, and Datadog, are always saying they are making AIOps, root cause analysis, and anomaly detection features, but even Splunk AppDynamics, these kinds of features are not working fine because of the nature of the metrics. Most of the customers are not supplying the hygiene of metrics. If you do not supply or make your environment's metrics hygienic, you cannot give the AIOps perspective to customers. The statement that these vendors can make root cause analysis automatically or have automatic detection features and capabilities cannot be truthfully said. To sum this up, this is not only a Splunk AppDynamics problem. From my personal perspective, this is all APM vendors' problem. The features that all these APM vendors need to improve are the AIOps features. These are really at the beginning of the AIOps era. Everyone is talking about AI, and it turns out to be a common hype in the technology market. We may see the real effect of this AIOps era maybe two or three years from today.

It is almost at the beginning of the story. When I started with Splunk AppDynamics, there was no acquisition between Splunk and AppDynamics, and AppDynamics was also its own company. This has been 14 years.

Implementation can be divided into two different parts. One part of the implementation process goes over the controller side, which can also be called the control plane side. One engineer is enough to install and prepare within two hours. However, the agent side is a bit more complicated because it depends on the customer's situation. If the customer has more than 100 or 1,000 different servers, mostly in production environments, we need to agree on when we deploy agents because we need to restart their applications. This creates some outages in their production environment. First, we need to agree on the timeline and project plan. It depends on the customer's decision. If we have a chance, at one time, we can also deploy more than 500 different agents at the same time, maybe within half a day, because we have really good playbooks and automation scripts working over Ansible, Chef, Puppet, or different automation tools that we can easily integrate. Implementation is easy, but the agent side depends on the customer's decision based on their project coverage or decision. It can take two days, or maybe two weeks or two months, depending on how big their environment is and how many licenses they get. For example, if they get more than 1,000 licenses for more than 1,000 hosts, it depends on their decision and project plan. It can take two months, one month, three weeks, or two weeks. It is a very variable thing.

I am working for my own business. Previously, I was in my former company, but I quit and built my own company. We are operating in the same area, and nothing has changed significantly in my life.

Over the last 14 years, we have made maybe more than 500 different installations, maybe much more than that. I do not know exactly, but in the last four years, we have prepared our own scripts and playbooks. It is really very simple to build a Splunk AppDynamics platform over the on-premises data center. Even if the customer wants to use the high availability option, if they have a limited environment or limited hardware resources, we can easily build all these components in one server. Because of that, it can be very simple when working only with one server. However, most customers in Turkey, including fintech-based, banking, government, and some really huge enterprises, need to use the high availability options, which means using more than six different separate servers. With our playbook and the solution's flexibility, Splunk AppDynamics is very flexible for this kind of model, and it takes no more than two, three, or four hours.

I would rate this solution an 8 out of 10.

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.

The major use case for Splunk AppDynamics is Application Performance Monitoring. We are implementing it to monitor our applications end-to-end.

The features and advantages I value most about Splunk AppDynamics include the L1 to L7 visibility we obtain on the application front. If you host any application, for example a website, you will get end-to-end information regarding application performance. Sometimes people say that the issue is latency, some people say it is an internet ISP side issue, and sometimes people say that it is on the SQL side and application performance. We have to get the end-to-end visibility. For example, people might use multiple APIs, and we need to determine whether the particular latency is because of the API, because of latency, or because of infrastructure. With Splunk AppDynamics, we will get this information completely.

Digital Experience Monitoring will help only if you implement the application agents across your endpoints. For example, I am in Chennai, India. Sometimes I will go to Singapore. If my applications are installed with the agent, it will provide complete visibility of how I am using the application and whether my experience is good. We are able to get context-wise information from the telemetry front.

Artificial intelligence in Splunk AppDynamics is helpful.

I see areas for improvement in Splunk AppDynamics. About reporting and anti-detection, I see room for additional features.

I started working with Splunk AppDynamics six months back.

My previous setup was Dynatrace, and we were using Dynatrace. Recently, we moved to Splunk AppDynamics for moving our SaaS platform to the cloud. Our applications are both on-prem and in the cloud, so we have moved to a hybrid model with Splunk AppDynamics.

The deployment of Splunk AppDynamics is straightforward.

I can quantify the return on investment with Splunk AppDynamics. When comparing Splunk with competitors such as Dynatrace and other products, I wonder if the difference is only in price or if there are also differences in terms of functions and capabilities.

The cost of Splunk AppDynamics compared to competitors is relevant. I think it is worth its cost.

I compare Splunk with competitors in terms of functions and capabilities.

I am using secure application features in Splunk AppDynamics. Splunk AppDynamics helps improve business resilience. I have seen many good aspects of the product and many advantages, while also identifying areas for improvement or concerns with the product. My overall review rating for Splunk AppDynamics is 32 out of 100.

We have been using Splunk AppDynamics for around one year and one month and started with just APM pieces for our back-end services and, over time, expanded it to cover business transaction and database monitoring.

The most valuable feature is the end-to-end transaction tracing, which provides genuine insights by allowing users to follow a single transaction across multiple microservices to pinpoint delays or errors, thereby saving hours during major incidents.

The auto-discovery and application mapping feature automatically maps out our entire application technology, showing service dependencies accurately, saving considerable manual configuration time.

The baseline and anomaly detection feature learns what normal looks like for your app, alerting on deviations beyond static thresholds.

A few things genuinely frustrate me about Splunk AppDynamics. First, the UI, while powerful, is dense and not modern compared to products like DataDog or New Relic, requiring a learning curve for new team members. Navigating feels unnecessarily deep, often requiring additional clicks.

Second, the alerting configuration is overly complex. Setting up health roles and policies isn't intuitive, leading to potential alert storms or missed incidents if configured incorrectly.

Lastly, the CPU-based licensing model complicates understanding costs with scaling, necessitating more straightforward processes.

We have been using Splunk AppDynamics for around one year and one month.

My experience with the application performance monitoring capabilities of Splunk AppDynamics has been largely stable. Issues with Splunk AppDynamics performance itself have been minimal. The agents are very reliable once deployed, running automatically without the need for manual intervention.

We contact technical support when we do the implementation and onboarding of Splunk AppDynamics, as it is part of our enterprise contract. Sessions with the solution engineer helped us in defining the initial architecture and sizing, which was fundamental.

We used DataDog previously, which offered a more extensive collection of frameworks, about seven or so. However, we've switched to Splunk AppDynamics for its straightforwardness, simplifying our processes.

The initial deployment is very straightforward if one reads the documentation correctly. All steps are clearly outlined in the documentation, making the setup hassle-free.

Technical support, part of our enterprise contract, assisted us during the implementation and onboarding of Splunk AppDynamics. We had sessions with a solution engineer for initial architecture and sizing, which was beneficial.

Pricing for Splunk AppDynamics is higher, attributed to the additional features it offers over other tools. While the cost is significant given we have around 120 services, it remains manageable and offers the value we're seeking.

Regarding the effectiveness of the features like auto-discovery and mapping, they visualize your application ecosystem. This feature is very useful to us because we don't have to do the manual effort. Using this feature has saved us around 20 to 30% of time. We don't need many people in the environment. If you have four to five people to handle that feature for 400 or 500 products, then we need only one to two people. Thus, it is resource-efficient and saves time.

We use AI-powered features in Splunk AppDynamics such as anomaly detection and root cause analysis. We have Splunk AppDynamics plus Splunk integration apps which eliminate the need for manual checks.

Using the APM, there are features in Splunk AppDynamics which allow for easy troubleshooting of code-level issues, removing the need for manual interventions.

Regarding the downsides of Splunk AppDynamics, we did not have major dislikes; most features are well-appreciated.

Splunk AppDynamics is a solution we recommend to our customers and vendors if they're within Splunk ecosystem, as it saves time and leverages the ecosystem's features.

Our overall review rating for Splunk AppDynamics is 9 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.

I work for a supply chain SaaS organization, and Blue Yonder 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 Blue Yonder, 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.