Monitoring in Microservices
summary
Factory 2.0 implements concrete checks that send realistic fake messages through the pipeline, verify database and API state, and email alerts on failure, so lost or delayed messages are detected and the failing stage is identified. Monitoring uses Prometheus + exporters for container metrics, an ELK stack (Elasticsearch, Logstash, Kibana) for logs, and Jenkins jobs running synthetic message checks every 10–15 minutes; playbook-driven listeners (Freshmaker/Greenwave integrations) replay and trace message flows, handling ~40–50 msgs/sec before load issues appear.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:28Container
- 2:58Pipeline
- 4:16Why Monitoring
- 5:34What we use
- 9:01What we didnt have
- 9:53Jenkins Job
- 15:06Apple Servers
- 16:15Jenkins
related talks
29m“If you Don’t Monitor your Infrastructure, you Don’t Own it!” Regain Control Thanks to Prometheus
10mMonitoring Microservices: A Challenge
41mMonitoring Like a Boss
34mPrometheus: Monitoring Microservice Applications
49mMonitor Your Microservices with Logs, Metrics, Pings and Traces
35mMonitoring Microservices
30mMeasuring Microservices
26mMonitoring Node.js Microservices on CloudFoundry with Open Source Tools and a Shoestring Budget