we have prometheus monitoring for production on going, it makes sense to monitor beta too. In practical terms this translates to:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| prometheus: add beta-specific instance | operations/puppet | production | +106 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T53494 Use Beta cluster as a true canary for code deployments (epic) | |||
| Stalled | None | T53497 Setup monitoring for Beta Cluster (tracking) | |||
| Resolved | fgiunchedi | T140646 deploy prometheus node_exporter for host monitoring | |||
| Resolved | fgiunchedi | T144502 deploy prometheus node_exporter and server to deployment-prep |
It'd be nice to have role::prometheus::node_exporter applied blanket to all of deployment-prep, I see classes at https://wikitech.wikimedia.org/wiki/Hiera:Deployment-prep is that what's that for?
Mentioned in SAL (#wikimedia-releng) [2016-09-15T15:53:52Z] <godog> add role::prometheus::node_exporter to classes in hiera:deployment-prep T144502
That works https://wikitech.wikimedia.org/w/index.php?title=Hiera:Deployment-prep&diff=839239&oldid=839131
But we still have a couple Precise instances and the puppet class does not work there. So the Hiera change has been reverted.
Mentioned in SAL (#wikimedia-releng) [2016-10-03T10:21:56Z] <godog> add role::prometheus::node_exporter to classes in hiera:deployment-prep T144502
Change 313816 had a related patch set uploaded (by Filippo Giunchedi):
prometheus: add beta-specific instance
Prometheus for beta is available at https://beta-prometheus.wmflabs.org/beta/graph and as a data source on https://grafana-labs.wikimedia.org/
Dashboard for host overview: https://grafana-labs.wikimedia.org/dashboard/db/prometheus-overview-per-project