My usual use cases for Splunk AppDynamics involve monitoring application performance issues.

I have used Splunk AppDynamics for business transaction monitoring. It helps us in prioritizing business transactions such as logins or checkouts because we can see the transactions, what problems they have, and what we need to do to fix them.

The most valuable features of Splunk AppDynamics that I have found so far include it being a deep-in monitoring solution for applications such as Java and databases. You can dig into the log information and performance information that is within the application. For a very easy setup, you have all the information that you need.

My impression of Splunk AppDynamics' AI-powered anomaly detection and root cause analysis in diagnosing performance issues is that it works and does the job. It's acceptable.

Regarding Splunk AppDynamics' line-of-code-level troubleshooting feature, specifically in diagnosing performance issues down to specific code lines, it relates to the database agent. The help is quite deep and quite useful. You get the code line error, and you are very fast on track to resolve the problem because you will be pinpointed into the real problem where the real problem is using Splunk AppDynamics for databases, for example. That's quite good.

My experience with the application performance monitoring capabilities of Splunk AppDynamics, particularly in on-premises environments, is that it works well for us. We can see that the best benefit is the service dependency mapping regarding different kinds of services. That's key—dependency mapping.

Splunk AppDynamics could be improved or enhanced as they are on track because they have the tools working with OTel. That is one thing I can mention since that has forced us to use other tools to monitor because of the price. Price is the key part here.

I have been working with Splunk AppDynamics for more than five years.

Based on my experience, Splunk AppDynamics has been very stable and reliable for us. As I have mentioned, we have run it for over five years, six or seven years I would say, and I think it's very stable with no problems with the agent or the setup.

I do not think we have counted on the scalability because our setup is not so large; it's quite a small setup, and that depends on the cost. We want to expand, but the cost is quite high.

I do not often communicate with the technical support. I think it's one or two times per year or something similar because it's so stable.

Based on my encounters with the technical support, I rate them at least seven, seven to eight. It depends on the technical question that we asked, but I think the support has been quite acceptable, more than acceptable. From my point of view, it's a seven to eight, which is more than acceptable.

Before Splunk AppDynamics, I used a different solution for these use cases.

The previous solution consisted of a number of different kinds of tools; I cannot go into details on that, but we used different kinds of other tools.

I participated in the initial setup and deployment of Splunk AppDynamics.

The process was very straightforward; there were a few components and steps that we documented and added internally because we are using Splunk AppDynamics as a SaaS solution. The setup is quite straightforward. Therefore, the setup is not an issue; it's working as designed.

Splunk AppDynamics provided technical help that assisted us in this process.

Regarding whether I have seen any return on investment so far regardless of expenses, I think we can say so because of the problems we had in the past and the fast way we solve problems with the tool. The technical person that is using this is quite happy when they know what to fix.

The overall positive impact and benefits I have seen from using Splunk AppDynamics so far is that the overall function is acceptable. Unfortunately, the setup is quite expensive, which is the bad part of it because I want to spread my agent across the IT landscape, but that's very expensive.

Overall, I consider Splunk AppDynamics an expensive product; it's very expensive.

Before choosing Splunk AppDynamics, I evaluated other options and other vendors.

I chose Splunk AppDynamics instead of the other options I had because of the deep insight you get with agents, especially for the databases and other application frameworks such as Java and .NET. You get quite useful information with a quite easy setup.

I am not using the secure application feature in Splunk AppDynamics.

I don't think we have tested Splunk AppDynamics' digital experience monitoring, so that's nothing.

I would rate this review overall as a six.

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.

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.

My main use cases for Splunk AppDynamics include APM, application performance monitoring.

The features of Splunk AppDynamics that I appreciate most are the business processes. These features benefit my organization by providing a bigger picture, not only of their own systems, however, how it influences other parts of the environment and how we are being influenced by other parts. For its time, Splunk AppDynamics helped improve my organization's business resilience quite a bit.

To improve Splunk AppDynamics, it should migrate seamlessly into observability Splunk, which is called Splunk Observability Cloud.

I have been using Splunk AppDynamics for around 15 years.

The stability and reliability of Splunk AppDynamics were okay. I did not experience unusual downtime, crashes, or performance issues; no software is perfect, but it was within the expected parameters.

Splunk AppDynamics had some confusion about the SaaS, no SaaS, only SaaS strategy, which wasn't clear. Some time ago, they committed again to on-premises, however, it was too late.

I evaluate customer service and technical support as good, seven out of ten.

Prior to adopting Splunk AppDynamics, I was not using another solution to address similar needs; this was our first step into the APM world.

My experience with pricing, setup costs, and licensing is that it was very expensive.

Sadly, I did not see return on investment with Splunk AppDynamics.

The solution I was using prior was Grafana Cloud.

What caused me to stop using the solution is that we failed to bring the product to our DevOps teams so that they could easily use it and learn how to use it, this is something we had to learn again. I would advise other organizations considering Splunk AppDynamics to take a sharp look at the whole Splunk product portfolio and how they merge to observability cloud, integrating many AppDynamics features; this is very interesting, but I don't know whether or not they are already there.

On a scale of one to ten, I would rate Splunk AppDynamics seven out of ten.

We had several applications that were facing performance issues. To improve our observability, alerting, and monitoring of these performance problems, we onboarded the applications onto Splunk AppDynamics. This allowed us to gain better insights into the issues and identify the business transactions that were causing the problems.

I haven't used the APM feature. It's primarily been configuring database collectors on a database.

Splunk AppDynamics has been effective in auto-discovery and mapping and visualizing our application ecosystem. There have been instances where we've needed to fine-tune the auto discovery feature. When we installed it on Unix and Windows applications, it retrieved a substantial amount of information. We then had to configure the information to meet our specific needs. The tool goes out and summarizes all the business transactions, but we need to limit or filter out the excess data. This is particularly important for gaining visibility into application performance and proactively resolving issues.

Using Splunk AppDynamics for business transaction monitoring significantly impacts my ability to prioritize transactions such as logins or checkouts, and it has improved the process.

I've worked on an application where users book trades into a system. Each booking translates into a transaction. Similarly, users query these trades, which corresponds to other transactions. I can see the speed of these transactions and identify issues when trying to write them into the database. I can also monitor when transactions are being queried. Additionally, there are other applications accessing the database, and I can observe their interactions as well. Overall, it enhances my ability to visualize what’s happening behind the scenes.

I find Splunk AppDynamics' AI-powered anomaly detection and root cause analysis to be very effective in diagnosing performance issues. I can quickly identify if there's any blocking on the database. Using the APM tool or the graphical user interface, I can track slow SQL queries. I can sort all those transactions to see which ones are consuming a lot of CPU and identify the long-running queries. This allows me to quickly assess the situation and understand what is going on.

Based on the issues we observe in Splunk AppDynamics, we know where to focus or where to spend money in improving the application. It gives us that flexibility to be able to improve and know where to focus our spending power.

I like the fact that you can self discover business transactions. It's easy to onboard your applications and configure your collectors or your agents.

The ability to monitor transactions and identify slow SQL queries in a database is valuable. We can detect issues such as blocking. It allows me to visually analyze the database's performance and understand its current state. Additionally, users can configure a dashboard to provide an overview of the database activities.

When I onboard applications onto AppDynamics, I configure database agents or collectors to gather metrics and monitor business transactions. This setup enables me to see what is occurring within the database environment. I have extensive experience in configuring agents and collectors for databases, as well as for Windows and Unix machines.

I would probably suggest making the tool more real-time and allowing for integration with a wider range of DevOps tools. This is particularly relevant when comparing it to something like Genius, which I recognize is a different tool altogether. Ideally, I would prefer a situation where I don't have to use two or three different observability tools, allowing me to focus on just one.

When you self-discover observable business transactions, there should be a better way to focus on the specific transactions that matter to us. In our environment, we have numerous business transactions, but not all of them are relevant for monitoring. It would be helpful to easily identify and target the business transactions we want to concentrate on without it being too cumbersome.

I've been using Splunk AppDynamics for about three to four years.

It has gotten a lot more stable over the years in comparison to when I first started using it. I would rate it a seven out of ten for stability.

It's easily scalable. I would rate it a seven out of ten for stability.

There are approximately 100 global users in my organization who work with Splunk AppDynamics.

The technical support for Splunk AppDynamics deserves a solid eight out of ten.

It's down to the complexity of our environment. We've got a lot of legacy applications, so it is a little bit complex trying to implement it. We had about 200 machines or databases. It took some time to get it implemented. It took a couple of months.

From an end user's perspective, I often need to coordinate with my infrastructure team. Ideally, I would like to implement it without having to rely on them. For example, if I don’t have full access to a database, I have to reach out to my infrastructure team to gain full access or to create a collector on the database. It would be much more efficient if I could log into the database and create a collector myself. In my experience, having to wait for administrators with full access to take action slows down the implementation process.

The only maintenance I could think of is having to make sure that the accounts are onboarded and the password is reset because the password sometimes expires. That's the only issue. It's quite straightforward. Once you reset those passwords, you're good.

I estimate it saves 10% to 15% in various resources.

Genius is likely more intuitive and offers greater functionality. It can be easily integrated with many other DevOps tools. In comparison to AppDynamics, Genius provides much more flexibility. However, one downside of Genius is that it does not automatically discover business transactions. From that perspective, AppDynamics has an advantage due to its self-discovery feature for transactions.

I would rate Splunk AppDynamics a seven 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.

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.

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

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

Splunk AppDynamics is no longer available as a standalone product in the market. Cisco has integrated it into their full-stack observability solution called the Splunk Observability Cloud. Therefore, purchasing Splunk AppDynamics as a standalone product is no longer an option, which presents a challenge for us. After Cisco acquired Splunk in 2023, Splunk AppDynamics, initially a separate product, became part of Cisco's full-stack solution. This change means that I can no longer deploy it as before.

Splunk AppDynamics does not support the complete MELT framework, which includes metrics, events, logging, and tracing for the entire stack. It lacks maturity in correlation within the observability spectrum. Splunk AppDynamics provides an end-to-end view of the application but misses the infrastructure part, which is crucial.

I have used this solution for nearly six years, dating back to 2019.

It is quite stable. We have faced challenges with Splunk agents and Splunk AppDynamics agents. You often have multiple agents running simultaneously in the infrastructure. This can sometimes cause conflicts with your application, so it is necessary to conduct appropriate testing before deploying them in production to prevent potential outages.

We are facing issues at the moment with Splunk and scalability. We have reached maximum capacity in our tier, and extending capacity has not been cost-effective from Splunk's perspective.

I would rate their support an eight out of ten.

I find the initial setup to be of medium to high complexity. It requires appropriate initial planning for the tools to be successfully implemented.

After implementation, it takes a little bit of time to realize its value.

We leveraged professional services from both Splunk and Cisco for the deployment of Splunk AppDynamics.

The pricing is quite comparable to similar solutions in the market. All these solutions at the moment are cheap, but it is like paying for insurance; you pay insurance to avoid major damage.

I would rate Splunk AppDynamics a seven out of ten. When addressing observability concerns, one should not only focus on the application layer. A full observability approach is required. New tools focus on the entire stack end-to-end, offering correlation to facilitate root cause analysis and minimize MTTR. Therefore, I would rate it a seven out of ten.

We analyze data for performance and availability, which is produced by servers, infrastructure and cloud. However, it's not sufficient to only use Dynatrace because it makes a lot of data. This data is interpreted by AppDynamics automatically with technical data to understand the business impact, thus improving productivity. In Europe, enterprises widely use SAP, and AppDynamics effectively supports this by monitoring the core IT environment and the services around SAP, like CRM, Salesforce, and logistics systems.

The alert mechanism in AppDynamics enhances server management tasks by using agents installed on each server. These agents capture numerous metrics, collaborate to describe specific transactions, and allow us to monitor each transaction based on user interactions. We can see where any transaction might falter in the SAP server, application server, or presentation database, helping us identify the exact point of failure or degradation in transaction time, extract anomaly detection, or pinpoint real failures in SAP or other applications. This mechanism is very similar to Dynatrace, but AppDynamics is currently the best option for SAP.

AppDynamics Server Monitoring lacks investment in new technologies like Kubernetes and cloud solutions. Dynatrace has received significant investment in these areas and is better suited for cloud-native applications. However, AppDynamics still holds value for traditional applications used in banks or larger companies.

I've worked with AppDynamics Server Monitoring for five to six years. My experience in monitoring systems started around 2020-2022, focusing on serviceability for SAP ERP environments.

Regarding stability, I would also rate it at nine out of ten as it is highly stable.

I'd rate the scalability of AppDynamics Server Monitoring at nine out of ten, indicating it's highly scalable.

AppDynamics Server Monitoring is deployed based on the organization's needs. For instance, installing it on a single server is better for a few clients for on-premises deployment. On the other hand, different solutions are available for cloud monitoring applications. The trend is shifting towards new paradigms like DevOps. AppDynamics adheres to these standards and can be used for both on-premises and cloud environments, depending on the specific requirements and business model of the organization. Maintenance requires a dedicated team, which can be extensive, especially in large organizations like banks.

I would rate my experience with the initial setup of AppDynamics as seven out of ten.

The return on investment with AppDynamics Server Monitoring has been significant in certain areas, especially for SAP environments. However, there hasn't been as much focus on the broader market due to their emphasis on cloud messaging applications. It ultimately depends on the customer's specific needs and how well the solution aligns with them.

The pricing for AppDynamics is expensive, but it is possible to negotiate special pricing through bids.

AppDynamics Server Monitoring is integrated into the infrastructure through agents installed on the servers, and it utilizes REST APIs for process control and integration with other solutions. In terms of AI usage, AppDynamics uses AI for anomaly detection and resource forecasting.

AppDynamics Server Monitoring is recommended, especially for SAP environments or cloud-native applications. However, the recommendation depends on the specific needs of the organization.

Overall, I would rate AppDynamics Server Monitoring as seven out of ten.

We use it to monitor the end-user responses of Oracle and Microsoft SQL. We still use OEM for deep dives.

The product provides visibility to the end-users who didn’t have visibility before.

Visibility to the end-users is a valuable feature.

The solution must improve security and setup. It runs off its own box now. The metrics could be standardized. It should add more databases.

I have been using the solution since 2016.

I rate the tool’s stability a seven out of ten.

I rate the tool’s scalability a six out of ten. We run quite a few servers.

I have used a lot of database monitoring products like OEM and SolarWinds SQL Sentry. We chose AppDynamics Database Monitoring because we bought APM.

The tool is deployed on the cloud, but we put an agent on-premise. The initial setup is straightforward. There are some complexities if we want additional features like automatic password rotation. We needed five people to deploy the product. It requires maintenance. There's not a great way to know when it's not reporting. We have to figure it out. It does not have a good alarm system to notify us when it stops.

We have seen a return on investment.

The price is okay.

We’re planning to replace the solution. It is a good tool. Overall, I rate the solution a six out of ten.

We use the product to monitor some of our critical systems. We started using the solution for application performance monitoring.

The product has the ability to drill down to the errors whenever we have issues.

The solution has performance issues after we deploy the agent.

I have been using the solution for about three years.

The product is stable.

The initial setup was easy.

The tool is expensive.

I recommend the solution to others. Overall, I rate the product a seven out of ten.