On 2/25/19 12:06 PM, Filippo Giunchedi wrote:

On Mon, Feb 25, 2019 at 6:40 PM Giovanni Tirloni <gtirloni@wikimedia.org> wrote:

  If we poke roles in the firewall so Icinga can reach the VMs and we
define the monitoring::service stuff in Puppet, is that all we need to
shutdown Shinken? Do you think there would be any concerns with going
that route?

I'm not sure, what checks does shinken do ATM that we'd need to port over to icinga? Right off the bat it seems simpler to me to fire up a icinga stretch VM and move over the checks and their puppetization to that VM instead, what do you think?

One of the reasons we haven't done this already is that WMF production monitoring seems to be in constant flux -- it's disappointing to adopt a monitoring tool only to have it deprecated a month later in production.  Is the current version of icinga that's running in prod actually your desired final state there, or is something else up and coming?


  I'm asking about this because soon we'll see requests about removing
more and more Jessie support from the Puppet codebase [0] and there's no
exit strategy from Jessie for Shinken (it's not available in Stretch
unless we want to package things ourselves, which I tried and failed).

Ouch! I didn't realize there's no shinken in stretch :( though it seems like a great occasion to get rid of it!


Cloud-admin mailing list