leap_platform.git/puppet/modules/site_check_mk, branch develop [leap_platform] [feat] Add check_mk config values, dont set them 2016-09-06T11:19:13+00:00 varac varacanero@zeromail.org 2016-09-06T09:45:58+00:00 67591d5f91b33bd8196137c14ea6ae4a01321aea When setting values like ignored_services = [...] this will override other `ignored_services` that might get parsed before. Instead, we use `+=` so multiple files can add sth to this config value. 
When setting values like

    ignored_services = [...]

this will override other `ignored_services` that might get parsed
before. Instead, we use `+=` so multiple files can add sth to this
config value.
[bug] Remove Nagios soledad procs check 2016-08-31T20:11:49+00:00 varac varacanero@zeromail.org 2016-08-31T20:11:49+00:00 9ef0d00b4302b7ddfc9d5620eeb4fad90d3a15aa leap_cli already checks for running procs - Resolves: #8380 
leap_cli already checks for running procs

- Resolves: #8380
Document site_check_mk::agent::soledad 2016-08-31T07:47:08+00:00 varac varacanero@zeromail.org 2016-08-31T07:47:08+00:00 1b4a1aaa6097e0fda72a7829ea3eb029a9e16c93 






ignore noisy 401 errors from soledad log.
2016-08-20T13:37:18+00:00

Micah
micah@leap.se

2016-08-16T18:23:16+00:00

31dfdfc32439980e92e6472a8392850e2c9b6bd0

Change-Id: Ia1764cb28e263353856523c11f351a39774bf3b4





Change-Id: Ia1764cb28e263353856523c11f351a39774bf3b4







Remove bigcouch (#8056)
2016-06-30T13:41:19+00:00

Micah
micah@leap.se

2016-06-28T17:16:47+00:00

d0ff379fe2a43d7968b8828c8b31af5254f6f85b

Change-Id: I0c6e27298c63bd37de1410985d054799818c22a4





Change-Id: I0c6e27298c63bd37de1410985d054799818c22a4







Merge remote-tracking branch 'origin/0.8.x' into develop
2016-06-07T09:41:04+00:00

varac
varacanero@zeromail.org

2016-06-07T09:41:04+00:00

d0ba04981366dd15e01cb89b970b01c18e8a4530












Reduce check_mk timeouts (#7807).
2016-05-31T19:39:59+00:00

Micah
micah@leap.se

2016-05-31T19:39:59+00:00

4d92b3a758e16fa2c7ee34a06272bd64a5c038ad

check_mk operations can take a long time (such as when doing a
re-inventory using "check_mk -II") when multiple hosts are down. This
decreases the connect timeout to 5 seconds.

Change-Id: I1eac5f14bad2afc2ffc4cbf8c950c24b052a0d6e





check_mk operations can take a long time (such as when doing a
re-inventory using "check_mk -II") when multiple hosts are down. This
decreases the connect timeout to 5 seconds.

Change-Id: I1eac5f14bad2afc2ffc4cbf8c950c24b052a0d6e







[feat] catch abnormal proc termination in syslog
2016-05-12T11:59:13+00:00

varac
varacanero@zeromail.org

2016-05-12T11:59:13+00:00

e35fca3d367a6294123a0d9a2c077f4db7dfe809

Sometimes a floating point exception or segfault of
a process results in systemd restarting it, we want
to recognize this from the syslog
i.e.:

  systemd[1]: pixelated-server.service: main process exited,
  code=killed, status=8/FPE
  systemd[1]: Unit pixelated-server.service entered failed state.

- Related: https://github.com/pixelated/pixelated-user-agent/issues/683





Sometimes a floating point exception or segfault of
a process results in systemd restarting it, we want
to recognize this from the syslog
i.e.:

  systemd[1]: pixelated-server.service: main process exited,
  code=killed, status=8/FPE
  systemd[1]: Unit pixelated-server.service entered failed state.

- Related: https://github.com/pixelated/pixelated-user-agent/issues/683







[bug] Run check_mk-refresh-inventory-daily after check_mk-refresh
2016-05-03T20:59:21+00:00

varac
varacanero@zeromail.org

2016-05-03T20:59:21+00:00

074c86322442ba73fe5ae07c9c07b1158c4d460d

Otherwise, the nagios config will get regenerated and nagios gets
reloaded before all checks are registered by a check_mk inventory.

- Related: #6873





Otherwise, the nagios config will get regenerated and nagios gets
reloaded before all checks are registered by a check_mk inventory.

- Related: #6873







[bug] run check_mk inventory on every puppetrun
2016-05-03T19:50:03+00:00

varac
varacanero@zeromail.org

2016-05-03T19:50:03+00:00

e9ebc834e7500dceefd0530ba6d0262e87855374

After upgrading the platform, there might be old check_mk checks
registered on the monitor hosts. We now run a check_mk inventory
on every run that also purged old non-existng checks.

- Resolves: #6873





After upgrading the platform, there might be old check_mk checks
registered on the monitor hosts. We now run a check_mk inventory
on every run that also purged old non-existng checks.

- Resolves: #6873