Metrics Monitoring

Monitor Everything Before Failures Happen

Section 1 – Welcome

L1 Welcome to Prometheus Monitoring Course

Section 2 – Prometheus and Grafana with Docker Compose

L1 Prometheus and Grafana with Docker Compose

Section 3 – Prometheus Query Language (PromQL)

L1 Prometheus Query Language (PromQL)

Section 4 – Creating Grafana Dashboards

L1 Creating Grafana Dashboards

Section 5 – Prometheus on Kubernetes

L1 Prometheus on Kubernetes

Section 6 – Prometheus Architecture

L1 Prometheus Architecture

Section 7 – MySQL Monitoring

L1 MySQL Monitoring

Section 8 – PostgreSQL Monitoring

L1 PostgreSQL Monitoring

Section 9 – MongoDB Monitoring

L1 MongoDB Monitoring

Section 10 – Redis Monitoring

L1 Redis Monitoring

Section 11 – Clean Up

L1 Final Clean Up

Section 12 – Extra Resources

L1 Instrumenting NestJS Apps with Prometheus Metrics

L2 Instrumenting Spring Boot Apps with Prometheus Metrics

L3 Instrumenting Express.js Apps with Prometheus Metrics

L4 Instrumenting Flask Apps with Prometheus Metrics

L5 Installing Helm on Mac and Windows

Redis Monitoring

Resources from Video Description

Key Takeaways

Redis Exporter – Exposes Redis metrics at its own /metrics endpoint for Prometheus to scrape.
Discovery via ServiceMonitor – A ServiceMonitor tells Prometheus where the exporter lives; kube-prometheus-stack setups typically require the release: prometheus label for discovery.
Kubernetes DNS & Cross-Namespace Access – Exporters reach Redis through the Service’s DNS/port (e.g., redis.database-monitoring.svc.cluster.local:6379), regardless of namespaces.
Secrets-Based Auth – Redis commonly uses password-only auth; the exporter can reference a Secret to authenticate securely.
End-to-End Flow & Health Signal – Exporter → Prometheus TSDB → Grafana dashboards; the redis_up metric (1 = up) confirms connectivity and scraping.