Splunk AppDynamics Reviews

We use AppDynamics mainly for troubleshooting the database side. If there is any issue that is happening, we go through layer by layer from the start of the application, for example, the UI layer. We go all the way to the database layer to show where the exact problems are. Additionally, we use it for other monitoring and alerting purposes.

The solution could be more user-friendly for diagnostic purposes. Anyone who is using the solution should be able to infer what that error is about, they should be able to troubleshoot it better.

I have been using AppDynamics for a year and a half.

AppDynamics has been stable.

I have found AppDynamics to be scalable.

We have 25 users using this solution in my organization.

We have previously used HP OpenView and Dynatrace. The client wanted to move from Dynatrace to AppDynamics and this is why we are using AppDynamics.

AppDynamics is easier to install compared to other solutions.

We have our own IT team that can support the installation. We have partners that can assist with the installation if needed.

There is a license to use this solution. However, the clients pay for the licenses we are the service provider.

I would recommend this solution to others.

I rate AppDynamics an eight out of ten.

It is primarily on-premises. We've been evaluating cloud, and I've got one application that's using a cloud-based solution, but the bulk of it is on-premises.

The business transaction that stands between multiple applications is proving to be most valuable.

Its resiliency can be improved. We're told that the best we can do with an on-prem solution is to have a hot standby that requires a manual switchover. So, it is a do-it-yourself Ikea model of maintaining data consistency between two servers, without having low balance or failover considerations for an on-prem solution.

There are a lot of capabilities and features that I need on a day-to-day basis that just are not included in the product. I have seen these capabilities and features in multiple other solutions. For number one, it has to be FedRAMP certified. We've been working around that with security and everything else. So, we need a solution that is fully supported in a secure federal environment.

I have been using it heavily for about two and a half years.

It was complex. There is nothing simple about this type of instrumentation.

We had professional services from AppDynamics or Cisco for mostly on-prem expertise.

I would advise others to take a higher systems-level approach to understand exactly what is needed in the way of instrumentation and monitoring within your enterprise. You can have a point solution like AppDynamics, and this is the big picture of the entire data flow throughout the system.

I would rate AppDynamics a six out of 10.

AppDynamics is used for performance management. It monitors the application's performance on a monthly basis.

I assist in the configuration of AppDynamics, which is used to measure the performance of the application.

AppDynamics will assist the company in managing its overall systems, capabilities, and performance. It will also assist the company in projecting the system's capacity.

Capacity planning is, in my opinion, the most useful.

While it is scalable, it could be better.

AppDynamics has been in place for a couple of years, but we only started using it this year.

AppDynamics is stable in terms of product features, but the core is a major concern.

AppDynamics is a scalable product.

I have not contacted technical support.

The initial setup is easier for the client.

In our environment, we already have the standard procedure in place to set up AppDynamics, to make it simpler.

I was not involved with the procurement of AppDynamic, but I believe it's expensive.

There are no minimum or maximum sizes; you can use AppDymaics regardless of your company's size. It is appropriate for small, medium, and large enterprises.

I would rate AppDynamics an eight out of ten.

We use AppDynamics for end-to-end monitoring solutions. Our organization is a crowd BPO and we have deployments in 128 countries.

We recently integrated with Azure Cloud and AWS CloudWatch. They have been designing their applications such that they require a lot of resources including CPU and memory. Using AppDynamics, we have been able to monitor what is happening using fantastic metrics that it provides. We have then been able to identify the root cause of problems.

The most valuable feature is that we can see how our end-users are interacting with our application across regions. We develop applications for Chrome, Safari, and Internet Explorer. We do not recommend people develop applications for Firefox.

There are a lot of plugins available.

Aternity is a better solution for internet monitoring, so that is an area that could be improved.

I would like to have customizable dashboards to use when I am monitoring certain applications. For example, AppDynamics does not need Power BI-related dashboards because it already supports such functionality. However, I would like to be able to include nicer gadgets or graphs, or perhaps more annotation.

I have been working with AppDynamics for approximately 15 years.

We have 30 to 40 or more applications running in AppDynamics right now, and we are expecting another 30 to 50 to be added in the next six months. This expected increase is the reason that we are evaluating other applications.

We have licensed technical support with AppDynamics and they are really good. 

My organization uses both AppDynamics and Aternity. AppDynamics and DynaTrace have higher ratings than Aternity; however, from a cost-optimization perspective, Aternity is better. It provides all of the APM features that the other tools are providing.

AppDynamics is more expensive than competitors.

As we continue to evaluate new products, those by New Relic will be ones that we look at.

I am a big fan of AppDynamics and it is a product I recommend.

I would rate this solution a nine out of ten.

It's mainly used to monitor both applications and databases. That's primarily how I use it.

Essentially, I use it for monitoring. I perform performance testing and use it to monitor database performance, CPU usage, and generate alerts on different nodes based on CPU utilization and other factors. It's mainly used to check the performance of the nodes.

I find it helpful, especially in terms of self-learning.

The major concern lies with reports, specifically their configurability. It's like, if I want to combine multiple reports and generate them all at once, that's not possible. Even though there's a setup for generating 25 reports, I wanted to group them all and generate them in one go, which isn't currently feasible. I have to manually run each report and set the time for it. There should be an option to schedule them collectively, like selecting 10 reports, setting a particular time, and having them scheduled.

The ability to schedule multiple reports at once, which is currently lacking. This is a challenge I face in my day-to-day work with AppDynamics.

I have been using this solution for more than a year.

It is a stable solution.

It's definitely scalable. The number of environments in our implementation has been increasing, so it's adaptable. It's a large enterprise, definitely not medium or small.

Maintenance is handled by the maintenance team.

In my experience, it's easy to use. There's nothing complex to learn or fear. You can quickly adapt to it without the need for extensive training. That's my advice.

Overall, I would rate the solution an eight out of ten.

We use AppDynamics Server Monitoring to keep track of live errors, loads, calls per minute, etc.

We can view the server activities, including issues in the process, with a single click. In the case of a script, we can create one branch to learn about function failure and the reasons behind it.

The product's initial setup process needs improvement.

We have been using AppDynamics Server Monitoring for six months.

It is a stable platform.

We have 150 AppDynamics Server Monitoring users.

Every organization has different requirements to set up servers. The configuration is tricky and requires a lot of tools. In such cases, getting assistance from the product's support team is easy.

The initial setup is complicated.

I rate AppDynamics Server Monitoring a seven out of ten. Its setup process is tricky. It is very different for every server. I recommend using Microsoft, Linux, and VMware as they have their monitoring tools.

We use AppDynamics Database Monitoring to identify high spikes in critical data, which helps us better understand when applications stop responding or are not responding well.

The solution can be deployed on-premises or in the cloud.

Data monitoring is the most valuable feature.

The price of the solution has room for improvement.

I would like the solution to be more customizable to meet our client's requirements.

I have been using AppDynamics Database Monitoring for two years.

I give the stability of AppDynamics Database Monitoring an eight out of ten.

I give the scalability of AppDynamics Database Monitoring a nine out of ten.

The technical support is excellent.

Positive

The initial setup is straightforward. The deployment takes two weeks and requires one architect and one developer.

We implement the solution for our clients.

The pricing is average. I give the price a five out of ten.

The license is paid on an annual basis.

I give AppDynamics Database Monitoring a ten out of ten.

We require five people to maintain the solution.

AppDynamics Database Monitoring only requires users to have a basic understanding of databases.

I use it to solve issues that my clients encounter, such as application slowness. It helps me identify whether the issue is related to the database, server, or CPU memory management.

Moreover, I use it to find solutions and provide recommendations to my colleagues.

This solution not only provides answers but also provides sensor data. This allows us to quickly resolve issues that developers may take a long time to solve. In essence, it helps us address problems at an early stage. Moreover, it is especially useful in production servers where real users encounter numerous issues.

There are numerous issues that arise during peak times, and AppDynamics makes it easy for us to identify the problem areas and determine the appropriate resolutions. This is how it helps us find solutions effectively.

Regarding improvements, I believe the dashboard could be more optimized. Although it claims to be optimized, I think it should be even more convenient, especially for advanced users. 

Additionally, the documentation can be a bit challenging. It would be beneficial if the documentation provided clear solutions for every problem. In my opinion, the documentation could be improved.

I worked with AppDynamics for around three to four months. I have been working directly with it for the past year.

I use the latest version. 

It is stable, but the only downside is the licensing part. Other than that, it's a reliable product with no major issues.

It is highly scalable. There are no additional limitations in terms of scalability.

In my company, we have around 50 to 100 clients using this tool. Although it can be a bit expensive, it is still being used extensively to solve various problems.

It's straightforward, not too complex. However, it requires proper learning to effectively use it.

The deployment process typically takes around one to two hours, depending on the system. Once the setup is complete, we can proceed with the implementation process.

First, there's a need for basic knowledge of OS, especially for Windows and .NET. Additionally, understanding concepts like Dynatrace and AppDynamics, their functioning, and architecture is crucial. These are the key methods involved in the deployment process. If it's a cloud solution, then AWS or Azure are the recommended options. If it's on-premises, then using either Linux or Windows is ideal.

For deployment, we need to focus on event configuration, which involves learning about network events and configuration. Once we understand this, we can proceed with the deployment setup. There is no frequent deployment. In case the deployment is not satisfactory, we may need to learn about Linux and Windows concepts.

I have seen some ROI. 

It is an expensive solution. It's on a yearly basis. We need to pay for it annually.

I have used Dynatrace. The main difference between the two is that AppDynamics utilizes different data mechanisms, while Dynatrace uses a unified agent approach. This simplifies the complexity of Dynatrace, providing more visibility and root cause analysis. In terms of benefits, AppDynamics is more scalable than analytics.

Overall, I would rate it a nine out of ten.