Adding Observability to HashiCorp Nomad Applications with Grafana
summary
Deploys Grafana, Prometheus, Loki, Tempo into a Nomad cluster (demo uses Vagrant) and shows concrete configs: Consul service discovery, Promtail for logs, and dashboards that switch from metrics to logs to traces. Claims Prometheus uses a Prometheus pull model, Loki stores only metadata so 10 TB of logs yields ~200 MB index, and Tempo indexes only trace ID allowing full-trace sampling. Demo services run but a VM disk-space issue prevents one trace jump; overall pipeline is functional.
AI-written summary · about
chapters (6)
- 0:00Introduction to observability
- 2:53What is observability?
- 7:11Grafana observability stack
- 13:30Demo with Nomad and Grafana
- 19:51Extending observability to Nomad
- 21:36Q&A and resources
related talks
21mMonitoring Nomad with Prometheus and Icinga
25mInspecting Nomad Events Using Grafana Loki
29mParanoid Observability –Success Stories and Misfortunes observing an observability stack
30mAutoscaling with HashiCorp Nomad
13mAutomate an Observable Runtime with HashiCorp and Ansible
27mFrom Zero Visibility to Full Observability with Grafana
35mFrom New Cluster to Insight. Deploying Monitoring and Logging to Kubernetes
27mObservability with Prometheus and beyond