
Overview

Product video
AppDynamics helps you visualize your entire application environment with our industry-leading Application Performance Monitoring (APM) solution - now that includes support for serverless environments like AWS Lambda.
With AppDynamics Serverless APM For AWS Lambda, you can discover, visualize, and map serverless application environments and dependencies and correlate the performance of those environments with end-user experience and business impact. This helps you solve performance problems much faster and find areas in your end-to-end environment that can be proactively improved.
This lightweight Lambda monitoring implementation reports directly to dedicated AppDynamics-managed serverless reporting endpoints and introduces minimal impact on application performance. Currently available for Lambda functions written in select languages. See the documentation resource link below for technical requirements.
Highlights
- Discover, visualize, and map application environments including serverless components and dependencies
- Automatically baseline system performance as well as business and conversion metrics to rapidly identify anomalies and their impact
- Leverage application insights to correlate application, end-user, and business data to improve SLAs, service adoption, and other performance KPIs
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/unit |
|---|---|
PDX - Serverless monitoring for AWS Lambda, requests (per 1000) | $0.001 |
PDX - Serverless monitoring for AWS Lambda, duration (per 1000 s) | $0.004 |
SYD - Serverless monitoring for AWS Lambda, requests (per 1000) | $0.001 |
SYD - Serverless monitoring for AWS Lambda, duration (per 1000 s) | $0.004 |
FRA - Serverless monitoring for AWS Lambda, requests (per 1000) | $0.001 |
FRA - Serverless monitoring for AWS Lambda, duration (per 1000 s) | $0.004 |
Vendor refund policy
By subscribing to this product you agree to terms and conditions outlined in the End User License Agreement referenced below.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
AppDynamics support team that is ready to help no matter what the issue is. Additional documenation is available here for Lambda support - https://docs.appdynamics.com/display/PRO45/Serverless+APM+for+AWS+Lambda
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.


Standard contract
Customer reviews
Unified observability has improved incident response and protects our digital user experience
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
Internal solutions were developed, but not third-party products prior to adopting Splunk AppDynamics.
How was the initial setup?
The deployment process of Splunk AppDynamics was done by the third-party consulting firm called HCL.
What about the implementation team?
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.
What other advice do I have?
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.
End-to-end tracing has reduced incident resolution time and now simplifies cross-service analysis
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using Splunk AppDynamics for around one year and one month.
What do I think about the stability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What about the implementation team?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Monitoring has improved banking app performance and now quickly identifies transaction bottlenecks
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Splunk AppDynamics for three to four years.
What do I think about the stability of the solution?
I would rate the stability of Splunk AppDynamics as an 8.
What do I think about the scalability of the solution?
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.
How are customer service and support?
Technical support for Splunk AppDynamics is fine, so I rate it 10. We are not facing any issues.
How was the initial setup?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Monitoring has improved proactive issue detection but agent management still needs simplification
What is our primary use case?
I am currently supporting Blue Yonder, where I implemented the Splunk AppDynamics solution for EY, Ernst & Young, and now I'm working with international companies, as you may be aware of Blue Yonder. I'm implementing Splunk AppDynamics for Blue Yonder, which has a variety of logistics and supply chain management applications to monitor, serving around 500 plus clients.
What is most valuable?
Predominantly, for this current project, we are using Application Performance Monitoring in Splunk AppDynamics, mainly for the Java instrumentations, as our application is completely based on Java, which helps to identify business transactions, bottlenecks, and also monitor database performance using custom queries.
I find the anomaly detection feature in Splunk AppDynamics quite good, as it was introduced about a year back, and we had enabled it.
Infrastructure monitoring in Splunk AppDynamics is really helping as it allows us to understand overall application performance and any bottlenecks, especially when we implement the machine agent alongside Application Performance Monitoring .
The main benefits from Splunk AppDynamics for my end users, mainly the application team, are that it helps identify bottlenecks proactively and allows for configuration of proper health rules to address issues before they affect customers.
What needs improvement?
I see that the main challenge with Splunk AppDynamics is the management of multiple agents, as installing several agents on a server is a significant hurdle we still face.
Functionality-wise, I would like to see more cognitive solutions in Splunk AppDynamics, ideally with a single agent that can implement policies and provide predictive insights regarding application performance degradation during peak times.
For how long have I used the solution?
I have been working with Splunk AppDynamics for almost five to six years.
What do I think about the stability of the solution?
I rate the stability of Splunk AppDynamics an eight, as I have not faced many stability issues with the product.
What do I think about the scalability of the solution?
Regarding scalability, I would also rate it an eight, as I have not encountered significant performance issues, especially being in a stable SaaS environment.
How are customer service and support?
With our premium support contract for Splunk AppDynamics, we are very satisfied, receiving consistent support including bi-weekly calls with customer success managers and product specialists.
Which solution did I use previously and why did I switch?
Currently, people are leaning toward Dynatrace , possibly due to its AI capabilities such as the Davis feature, which offer a single agent concept that is easier to implement and maintain.
How was the initial setup?
For Splunk AppDynamics, the initial setup process I've encountered has been simple since I only increased the scope of what was already established four years ago, and while there is a challenge with multiple agent solutions, the product is generally beneficial.
What about the implementation team?
We purchase Splunk AppDynamics through our vendor, HCL Technologies, as they handle all sales instead of direct from the vendor.
Which other solutions did I evaluate?
In my opinion, the main competitor to Splunk AppDynamics in the market is Dynatrace .
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Unified asset monitoring has improved on-prem control and strengthened security insights
What is our primary use case?
My usual use cases with Splunk AppDynamics are primarily related to the Innova project, where we collect all assets and prepare a dashboard to display all assets and create reports for management about what assets are in place, their numbers, and their identifications.
We use Splunk AppDynamics for application performance monitoring in on-premises environments because hybrid is not an option for us, as we utilize an OT system located on the client's premises, and we do not use a hybrid or any cloud environment.
We use Splunk AppDynamics primarily for maintenance and support, especially given the current threat landscape. We validate all software and hardware lists approved by the end user and monitor for any recently added assets to ensure compliance with the approved repository.
What is most valuable?
I rate Splunk AppDynamics' line-of-code level troubleshooting feature a perfect 10 out of 10 for diagnosing performance issues, as it is very good.
The codes used for Splunk are very good, understandable, and readable, which is why I give it a high rating.
I find Splunk AppDynamics' Digital Experience Monitoring feature very good because it offers end users complete insights into their network, hardware, and software assets, along with detailed reporting on asset installation, models, and operating systems.
The Secure Application feature in Splunk AppDynamics is valuable because it links to the firewall and reports any incidents or unexpected asset discoveries, thereby preventing unauthorized access or communication within the network.
What needs improvement?
I do not believe there are areas to be improved in Splunk AppDynamics rather than the current situation, but I believe that integrating artificial intelligence and linking the software with other APIs, such as AI or machine learning, would be great.
I wish to improve the AI and machine learning capabilities in the software, which are currently used for top management reporting instead of manual reporting from the system. I believe AI could provide more insights for annual or half-yearly reports and forecast future changes in the asset landscape.
For how long have I used the solution?
I have been working with Splunk AppDynamics for approximately two years.
What do I think about the stability of the solution?
I give Splunk AppDynamics a 10 out of 10 for stability and reliability since it offers full insights into the software and hardware supply list.
Both stability and reliability are excellent in Splunk AppDynamics, with my assessment reflecting its consistent performance.
I have never experienced any outages with Splunk AppDynamics; it has never stopped working abruptly.
What do I think about the scalability of the solution?
Scalability is very good in Splunk AppDynamics as it can accommodate a wide range of asset counts, but it depends on the license schema, which may range from 250 to 10,000 assets.
How are customer service and support?
I normally communicate with the technical support of Splunk AppDynamics for any incidents or issues, but we have not opened any tickets yet. We also have 40 optional support hours committed in our contract.
Currently, I have not communicated with any technical support specialists from Splunk AppDynamics because we are still in the integration phase, but if we face issues during testing, we will use the support hours we have committed.
Which solution did I use previously and why did I switch?
Before using Splunk AppDynamics, I used an outdated solution, an Excel sheet, to track all assets, software, and hardware, which was challenging compared to the resilience that Splunk AppDynamics' dynamic software provides.
How was the initial setup?
My experience with the initial setup and deployment of Splunk AppDynamics is that it was very easy, with our team installing it in four control centers in less than eight days, which I find to be perfect.
What about the implementation team?
We requested all technical manuals and third-party documentation from Splunk AppDynamics to deliver them to the end user as part of my commitment, ensuring they receive all necessary documentation and training materials.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing of Splunk AppDynamics are managed by another team called the resource team, and they handle all tool and software lists to provide us with the necessary licenses.
I consider the pricing of Splunk AppDynamics to be mid-range compared to other software, as it operates on a subscription model, and the resource team finds the best prices, ensuring that Splunk AppDynamics is an acceptable option for the end user.
Which other solutions did I evaluate?
I evaluated other vendors, but we chose Splunk AppDynamics because the customer provided a list of approved software that we were required to procure and install without deviations.
What other advice do I have?
I have experience with IT asset management solutions, specifically with Device42 , and also with asset discovery tools such as Splunk AppDynamics and other tools.
I was working in one of the projects in the Western region of Saudi Arabia at Neom city, where it is called the Innova project, and we are using Splunk AppDynamics for technical purposes there.
My role is as a delivery manager, and I am taking care of all software and hardware delivery at GE Vernova, where I have a team of integrators, network engineers, and database engineers. I ensure that everything has been delivered correctly to the end user and customer.
I am not in charge of getting into the technical details, but I follow up on the software names to ensure they are configured and in place, and I see that the automatic asset discovery feature, which automatically detects any additional hardware, is very interesting.
I think Splunk AppDynamics' data collection feature with agents or OpenTelemetry is perfect because it is installed dynamically on all servers and nodes, and all agents respond quickly to the server or master station where Splunk AppDynamics is installed, providing great insights into hardware and software discovery.
Both stability and reliability are excellent in Splunk AppDynamics, with my assessment reflecting its consistent performance.
The alerting feature greatly impacts end-user experience since it is user-friendly and the end users are well-trained by GE, making them capable of understanding and operating the software without complications.