Performance monitoring and management training teaches engineers and developers to find and fix application bottlenecks using AppDynamics, now Splunk AppDynamics. Participants instrument applications, read business transactions and flow maps, set health rules and baselines, and troubleshoot slow code and databases. Bodhih runs it as a 3-day lab or six 3.5-hour live virtual sessions.
- Delivered in person at your location or as live virtual sessions
- Designed with the ADDIE model and evaluated for behaviour change
- Offered by Bodhih since 2008 to 2,000+ organisations across 7 regions
Where and how: performance monitoring and management training as an in-person workshop in Bengaluru, Mumbai, Delhi NCR, Gurugram, Hyderabad, Chennai, Pune, Kolkata, Ahmedabad and Jaipur; as a live online course; or delivered overseas in Dubai, Singapore and across the Middle East, Asia and Africa.
Last reviewed by Siddharthan VGJ, Founder · Bodhih Training, Bengaluru
App dynamics
Program Overview:
AppDynamics is the leading tool that helps analyze, optimize and predict bottlenecks in complex information systems. It can be done on site, during product test and deployment and on the cloud. It has agents for .Net, node js, PHP, Java, C++, Python, Apache Web Server and GoLang.
Training Duration:
Ideally this training is for 3 days but can be customized as per the need of the client.
Target Audience:
This Program is specially designed for Engineers and developers who can apply the AppDynamics concepts.
Training Outcome:
- Practical Approach
- Hands on training session
- Real time project and case studies
- 24/7 support
Solutions & Services
What participants will be able to do
Instrument applications correctly
Install and configure agents for your stack and confirm that tiers, nodes and backends appear as expected.
Think in business transactions
Identify, name and prioritise the user journeys that matter so monitoring reflects business impact.
Diagnose slow and failed requests
Use snapshots, call graphs and flow maps to trace a problem to the method, query or external call behind it.
Alert on what matters
Build health rules and policies on dynamic baselines so teams are notified about real deviations, not noise.
Monitor the whole path
Correlate application metrics with database, server and end-user experience data.
Share insight through dashboards
Create dashboards and reports that developers, operations and managers can each use.
Who should attend
- Application developers working on Java, .NET, Node.js, PHP, Python, Go or C++ services
- Site reliability and DevOps engineers responsible for production health
- Performance and load testing engineers
- Support and operations teams handling incident triage
- Technical leads setting monitoring standards for their teams
Recommended program outline
Recommended design, customised to your context after a short needs analysis.
01APM foundations and architectureModule 1 · Half day+
- Why application performance monitoring matters for modern distributed systems
- Controller, agents, applications, tiers, nodes and backends
- SaaS versus on-premises deployment considerations
- Where APM fits alongside logs, infrastructure metrics and observability tools
02Agent installation and configurationModule 2 · Half day+
- Installing app server agents for the team's language stack
- Machine and database agents for infrastructure visibility
- Verifying data flow and common setup issues
- Agent configuration practices for development, test and production
03Business transactions and flow mapsModule 3 · Half day+
- How business transactions are detected and customised
- Reading flow maps to see dependencies and slow calls
- Grouping and excluding transactions to keep data meaningful
- Identifying the handful of transactions that matter most to users
04Troubleshooting in practiceModule 4 · 1 day+
- Transaction snapshots, call graphs and error analysis
- Diagnosing slow database queries and external service calls
- Lab: finding the root cause in a deliberately broken sample application
- Building a repeatable troubleshooting checklist for incidents
05Health rules, baselines and alertingModule 5 · Half day+
- Dynamic baselines and how anomalies are judged
- Writing health rules, policies and actions
- Reducing alert fatigue with sensible thresholds
- Integrating alerts with the team's incident and on-call process
06End-user monitoring and dashboardsModule 6 · Half day+
- Browser and mobile real user monitoring concepts
- Custom dashboards for developers, operations and managers
- Capstone: a monitoring plan for the team's own application
- Presenting findings to developers, operations and business stakeholders
Sample training plan: 3-day hands-on design
This three-day lab teaches engineers to use AppDynamics application performance monitoring the way production teams need it. Participants instrument a sample e-commerce application with agents for their own language stack, define the business transactions that matter, and then hunt real faults: a slow database query, a failing payment call and a memory leak injected by the facilitator. They write health rules on dynamic baselines, cut alert noise, build dashboards for three audiences and finish by presenting a monitoring plan for their own application.
Participants can explain the monitoring architecture and instrument a multi-tier application end to end.
- 09:30–10:00The 2 a.m. callEnergiser
- 10:00–10:45How the platform sees an appConcept burst
- 11:00–12:15Agent installation labHands-on lab
- 12:15–13:00Setup fault findingGroup challenge
- 13:45–14:45Which transactions matter?Case clinic
- 14:45–15:30Custom transaction rulesDemo & practice
- 15:45–16:45Map your own applicationBuild sprint
- 16:45–17:30Day one retroReflection
Participants can find the root cause of slow and failing requests quickly and repeatably.
- 09:30–10:00Flow map detectiveEnergiser
- 10:00–11:00Snapshots and call graphsDemo & practice
- 11:15–12:30Broken app, round oneHands-on lab
- 13:15–14:30Broken app, round twoSimulation
- 14:30–15:15Database and external callsHands-on lab
- 15:30–16:30Troubleshooting checklistPeer coaching
- 16:30–17:30Day two retroReflection
Participants can alert on what matters, see the user's experience and share insight with each audience.
- 09:30–10:00Alert fatigue quizEnergiser
- 10:00–11:15Health rules on baselinesHands-on lab
- 11:30–12:15Alerts in the on-call processCase clinic
- 12:15–13:00End-user monitoringDemo & practice
- 13:45–14:45Three dashboards, three audiencesBuild sprint
- 14:45–15:30Capstone: monitoring planBuild sprint
- 15:45–16:45Capstone reviewPresentation
- 16:45–17:30My 90-day monitoring planAction planning
Every session’s activity, timings, outputs and materials, plus pre-work, a 90-day reinforcement plan and how impact is measured. Free, emailed to you instantly.
Recommended: 3 days in person (09:30–17:30) as a lab on a sample multi-tier application, or 6 × 3.5-hour live virtual sessions; customisable to your stack. A sample design: every Bodhih program is customised after a short needs analysis.
How long is performance monitoring and management training?
The recommended design is three days of hands-on labs, 09:30 to 17:30, or six live virtual sessions of about three and a half hours. A shorter two-day version focuses on instrumentation, troubleshooting and alerting, and the program is customised to your language stack.
What activities are included in performance monitoring and management training?
Participants instrument a sample e-commerce app, curate business transactions, diagnose injected faults such as a slow query, a payment timeout and a memory leak, tune health rules to cut alert noise, build dashboards for three audiences and present a monitoring plan for their own application.
Frequently asked questions
What is AppDynamics used for?
AppDynamics is an application performance monitoring tool. It traces requests as they move through services, databases and external calls, measures response times against learned baselines, and highlights where a slowdown or error starts. Teams use it to find bottlenecks during testing and to resolve production incidents faster. It is now offered as Splunk AppDynamics.
How long does AppDynamics training take?
Bodhih recommends 3 days for this program, which leaves time for hands-on labs on instrumentation, troubleshooting and alerting. It can be customised to your needs, for example a shorter version for support teams who mainly read dashboards, or deeper sessions for engineers configuring agents across a large estate. Live virtual delivery is also possible.
What is a business transaction in AppDynamics?
A business transaction represents a user request as it flows through your application, such as login, search or checkout. AppDynamics groups similar requests into these transactions so you can see performance by the actions that matter to the business. Understanding how they are detected and named is one of the first skills taught in the program.
Does this training prepare teams for an AppDynamics certification?
The program covers the core concepts of instrumentation, business transactions, troubleshooting, health rules and dashboards, which helps teams prepare for the vendor's own certification if they choose to pursue it. Bodhih does not conduct the vendor's certification exams. The focus is practical skill on your team's applications. Labs use sample applications or, where approved, your own test environment.
What is the difference between monitoring and observability?
Monitoring tells you when known metrics cross a threshold, such as response time or error rate. Observability is the wider ability to understand why a system behaves as it does, using metrics, traces and logs together. The program shows how APM traces fit into this picture and where they connect with infrastructure and log data.