Page MenuHomePhabricator

Get the clouddb-services systems into Shinken and possibly icinga
Closed, DuplicatePublic0 Estimated Story Points

Description

Monitoring is almost non-existent since we moved toolsdb and osmdb into VMs. We need to fix that as soon as possible.

This is meant to be the general server monitoring piece of T220530, which is more of the db-monitoring piece.

  • Basic Shinken Alerts
  • Service-specific Shinken
  • Check on Icinga Possibilities

Event Timeline

Bstorm created this task.

@aborrero mentioned https://gerrit.wikimedia.org/r/c/operations/puppet/+/499516 in meeting today, but I think (especially since that may not be complete), that should be added to in the course of this rather than being a blocker for getting this in shinken. Unmonitored DBs is very bad.

Change 502568 had a related patch set uploaded (by Bstorm; owner: Andrew Bogott):
[operations/puppet@production] clouddb-services: add some rudimentary monitoring

https://gerrit.wikimedia.org/r/502568

Change 502568 merged by Bstorm:
[operations/puppet@production] clouddb-services: add some rudimentary monitoring

https://gerrit.wikimedia.org/r/502568

Andrew lowered the priority of this task from High to Medium.Jan 14 2020, 5:36 PM
Andrew moved this task from Soon! to Blocked on the cloud-services-team (Kanban) board.

shinken instance and puppet module have been deleted. this leaves just the icinga part and / or is blocked by T250206

Overall, this is already being monitored via the system at T250206. I'll merge this in.