Fundamentals to Advanced | Theory + Practical Hands-on Labs
Training Duration: 3 Days (18 Hours – 6 Hours per Day, excluding breaks)
Level: Beginner → Intermediate → Advanced
Target Audience: DevOps Engineers, SREs, Cloud Engineers, System Administrators, Developers, and IT Operations Teams
Training Approach: 40% Theory + 60% Hands-on Labs
Day 1 – Elastic Observability Fundamentals, Agent Setup, Log Monitoring & Data Ingestion
Foundation
Objective: Understand Elastic Observability architecture, configure Elastic Agents, collect logs, and learn how to ingest, search, parse, and analyze monitoring data.
| Module | Topics / Agenda | Duration |
|---|---|---|
| 1. Introduction to Observability | What is Observability? Monitoring vs Observability, Logs, Metrics, Traces, benefits, use cases, and industry examples | 60 min |
| 2. Elastic Observability Architecture | Elasticsearch, Kibana, Fleet, Elastic Agent, integrations, data streams, OpenTelemetry, and end-to-end data flow | 45 min |
| 3. Elastic Agent Setup & Configuration | Fleet-managed vs standalone agents, installation, enrollment, agent policies, System integration, agent health, and troubleshooting | 90 min |
| 4. Log Monitoring & Analysis | Collecting Linux and application logs, centralized log monitoring, Kibana Discover, KQL, ES|QL basics, filtering, searching, and troubleshooting | 90 min |
| 5. Data Ingestion & Parsing | Data ingestion methods, ingest pipelines, JSON logs, Grok and Dissect processors, timestamp extraction, Elastic Common Schema (ECS), and data validation | 75 min |
Hands-on Labs – Day 1
- Lab 1: Explore the Elasticsearch, Kibana, and Fleet environment.
- Lab 2: Install and configure a Fleet-managed Elastic Agent.
- Lab 3: Collect Linux system logs and custom application logs.
- Lab 4: Search and analyze logs using Kibana Discover, KQL, and basic ES|QL.
- Lab 5: Create an ingest pipeline to parse and structure sample logs.
Day 1 Outcome: Participants can configure Elastic Agents, collect and parse logs, and investigate operational events using Kibana.
Day 2 – Metrics Monitoring, APM, Uptime Monitoring & Kibana Dashboards
Intermediate
Objective: Monitor infrastructure and applications, investigate performance problems, configure availability monitoring, and build observability dashboards.
| Module | Topics / Agenda | Duration |
|---|---|---|
| 6. Infrastructure & Metrics Monitoring | CPU, memory, disk, network, host monitoring, infrastructure inventory, metrics analysis, infrastructure integrations, and resource utilization | 90 min |
| 7. Application Performance Monitoring (APM) | APM architecture, instrumentation, Elastic APM and OpenTelemetry, transactions, spans, distributed tracing, latency, throughput, errors, and service dependencies | 105 min |
| 8. Uptime & Synthetic Monitoring | Availability monitoring with Elastic Synthetics, HTTP, TCP and ICMP checks, browser monitoring concepts, response times, and availability testing | 60 min |
| 9. Kibana Dashboards & Visualizations | Kibana Lens, charts, tables, metric panels, filters, time ranges, dashboard creation, customization, and sharing | 75 min |
| 10. Observability Correlation | Correlating logs, metrics, and traces, service health, service-level indicators (SLIs), and service-level objectives (SLOs) | 30 min |
Hands-on Labs – Day 2
- Lab 6: Configure and visualize Linux infrastructure metrics.
- Lab 7: Instrument a sample application and analyze APM transactions, traces, and errors.
- Lab 8: Configure HTTP availability checks using Elastic Synthetics.
- Lab 9: Create a custom Kibana dashboard combining system and application metrics.
- Lab 10: Correlate application errors with logs and infrastructure performance.
Day 2 Outcome: Participants can monitor host health, analyze application performance, configure synthetic checks, and build operational dashboards.
Day 3 – Advanced Alerting, Troubleshooting, Root Cause Analysis & Best Practices
Advanced
Objective: Build proactive monitoring, automate alerts, troubleshoot incidents, apply observability best practices, and perform end-to-end root cause analysis.
| Module | Topics / Agenda | Duration |
|---|---|---|
| 11. Alerting & Notifications | Alerting concepts, rule types, metric/log/APM/synthetic alerts, thresholds, connectors, email, Slack, webhooks, notifications, and alert noise reduction | 90 min |
| 12. Troubleshooting & Root Cause Analysis | Systematic incident investigation, log correlation, APM traces, performance bottlenecks, latency spikes, resource saturation, errors, and RCA workflow | 90 min |
| 13. Advanced Observability Features | ES|QL analysis, anomaly detection concepts, ingest pipeline optimization, data quality, retention, data stream lifecycle, and observability cost management | 60 min |
| 14. Observability Best Practices | Golden Signals, RED and USE methods, monitoring design, SLI/SLO definitions, dashboard standards, alert tuning, security, scalability, and production readiness | 60 min |
| 15. End-to-End Practical Project | Implement observability for a sample application, generate an incident, detect the issue, investigate root cause, and demonstrate resolution | 60 min |
Hands-on Labs – Day 3
- Lab 11: Create CPU, memory, log error, and application latency alerts.
- Lab 12: Configure and test an alert notification connector.
- Lab 13: Investigate simulated high CPU, slow response time, and application errors.
- Lab 14: Analyze advanced queries and review data retention configurations.
- Lab 15: Complete an end-to-end incident detection and root cause analysis exercise.
Day 3 Outcome: Participants can create production-oriented monitoring and alerting, investigate incidents, identify probable root causes, and implement observability best practices.
Three-Day Training Summary
| Day | Focus | Level |
|---|---|---|
| Day 1 | Observability fundamentals, architecture, Elastic Agent, logs, ingestion, and parsing | Beginner |
| Day 2 | Infrastructure metrics, application monitoring, APM, synthetic monitoring, and dashboards | Intermediate |
| Day 3 | Alerting, notifications, advanced analysis, troubleshooting, RCA, and production best practices | Advanced |
Recommended Lab Environment
Participants should have access to an Elastic Cloud deployment or a prepared self-managed Elastic Stack, a Linux VM with permissions to install Elastic Agent, a sample application capable of producing logs and traces, and the necessary Kibana/Fleet privileges. Alert connectors and synthetic monitoring facilities should be prepared before training.
Important platform note: This agenda uses Elastic Synthetics for uptime and availability monitoring because the legacy Uptime application is deprecated. Fleet-managed Elastic Agent is used as the primary collection method, with OpenTelemetry introduced for modern application instrumentation. Some advanced features may depend on the selected deployment and subscription. Elastic Docs+3
Expected Learning Outcomes
By the end of this three-day program, participants should be able to:
- Explain Elastic Observability architecture and monitoring concepts.
- Install, configure, and manage Elastic Agents using Fleet.
- Collect, ingest, parse, search, and analyze infrastructure and application logs.
- Monitor infrastructure performance using metrics.
- Configure APM and analyze application transactions and distributed traces.
- Set up synthetic availability monitoring.
- Design and build Kibana dashboards.
- Configure proactive alerting and notifications.
- Troubleshoot incidents and perform root cause analysis.
- Apply production observability best practices for reliability, performance, scalability, and cost efficiency.
Recommended final deliverable: Each participant builds a working observability solution for a sample application, including log collection, infrastructure metrics, application traces, uptime checks, a Kibana dashboard, alerting rules, and a completed incident investigation.