Monitoring Multiple Cloud Providers Made Easy
summary
Elasticsearch centralizes logs and metrics from AWS, Azure and GCP using Filebeat, Metricbeat and the serverless Functionbeat. Metricbeat pulls 16 metric sets from AWS (incurring CloudWatch API charges), Filebeat reads S3/Event Hub/Stackdriver sinks, and Functionbeat deploys as a Lambda that watches the CloudWatch log group "Apache access logs" (uploads a CloudFormation package to S3, creates Lambda and IAM roles) and ships raw log messages to Elasticsearch (data arrives in ~2–3 minutes; use ingest pipelines to split message fields).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:47Challenges in multi-cloud monitoring
- 5:02Monitoring AWS logs and metrics
- 16:32Monitoring Azure logs and metrics
- 19:02Monitoring GCP logs and metrics
- 23:23Adding APM to observability
- 28:49Demo: Function Beat for serverless monitoring
- 48:08Q&A and closing remarks
related talks
34mMonitor Kubernetes cluster with Elastic
49mMonitor Your Microservices with Logs, Metrics, Pings and Traces
30mUsing Open Source Observability with Lambda
34mObservability in Serverless Application
35mFull Stack Visibility with Elastic: Logs, Metrics and Traces
44mThe Holy Trinity of Observability: Logs, Metrics, and Traces
31m360° Monitoring of Your Services
43mPractical Application Logging and Monitoring
