Change Details

Following from {T233675}. We have a dashboard: * <https://grafana.wikimedia.org/d/BvWJlaDWk/startup-manifest-size> And it monitors group1 (e.g. hewiki, commons, wikidata) and group2 (e.g. enwiki) currently. To do: * {icon square-o} Enable the maintenance cron on Beta Cluster. * {icon square-o} Add a group0 wiki to the production maintenance cron iteration (e.g. a closed wiki) * {icon square-o} Create an alert dashboard based on the startup-manifest-size dashboard, with queries for one wiki in each group. * {icon square-o} Register the new dash in operations/puppet for Grafana alerting.

Following from {T229836} and {T233675}. We have a dashboard: * <https://grafana.wikimedia.org/d/BvWJlaDWk/startup-manifest-size> And it monitors group1 (e.g. hewiki, commons, wikidata) and group2 (e.g. enwiki) currently. To do: * {icon square-o} Enable the maintenance cron on Beta Cluster. * {icon square-o} Add a group0 wiki to the production maintenance cron iteration (e.g. a closed wiki) * {icon square-o} Create an alert dashboard based on the startup-manifest-size dashboard, with queries for one wiki in each group. * {icon square-o} Register the new dash in operations/puppet for Grafana alerting.

Following from {T229836} and {T233675}. We have a dashboard: * <https://grafana.wikimedia.org/d/BvWJlaDWk/startup-manifest-size> And it monitors group1 (e.g. hewiki, commons, wikidata) and group2 (e.g. enwiki) currently. To do: * {icon square-o} Enable the maintenance cron on Beta Cluster. * {icon square-o} Add a group0 wiki to the production maintenance cron iteration (e.g. a closed wiki) * {icon square-o} Create an alert dashboard based on the startup-manifest-size dashboard, with queries for one wiki in each group. * {icon square-o} Register the new dash in operations/puppet for Grafana alerting.