Age | Commit message (Collapse) | Author |
|
The rationale here is:
- bigcouch/its included erlang version is incredibly noisy and spits out
warnings/error msgs all the time
- it uses the worst logging format i ever saw, multiple lines directly
to a file (couch 2.0 uses lager as logging backend which can log to
syslog)
- trying to sort out the false positives will take too much time,
and who knows which of them will be resolved in couch 1.6/2.0
Change-Id: Idbe6b37a19cd65ce31a50d4c28eedb4cf15ba3b5
|
|
Increase warning/critical thresholds for time between tapicero heartbeat
checks so it will emit less false positives
Change-Id: I0f97373d88658b7f17b2c4e8c1963198dc3f66ed
|
|
Change-Id: Ie7943c9a541c3cd2feac7686ed1092aadc5a7c7a
|
|
These are warnings that might have different origins, each of
them we don't want to alarm the admin:
- A bitmask client bug (user will poke the client devs if things
break, and they will go after it)
- A simple network failure, packets might get cut of
- Malicious user tries to temper with TLS handshakes - this gets
more interesting, but still (like ssh bruteforce attacs) an admin
would not want to get annoyed by this by default, but they still
have the option to use log analysers of their choice if they want
to investigate this.
Change-Id: I23ca3b700e41f22f34ad3346ed4e647b86000bb2
|
|
Change-Id: If844b95c44e697f480df8ee2ae6607709b9942f7
|
|
Change-Id: I7b778e1e1af2784bd79840f20453ca8718927e25
|
|
Change-Id: I51ce8a9e8773d267c270a1725a497f9a43f2e9ff
Sidenote: $nagios_hosts was never used
|
|
Change-Id: I115ebdefd7365bf15a30c4a3ce7a4543ad757cec
|
|
Change-Id: Ibefc6ce08cf714cf79a460a8b6eb32e2851ce22c
|
|
condition with another tapicero instance #6534
Change-Id: Ie194a2983210601bd24aef5e74f8b7fa2b7c433f
|
|
|
|
their own files, fix mx logwatch path.
|
|
/var/log/tapicero, fix webapp logwatch location.
|
|
|
|
leap_couch_stats.sh is a local check_mk agent script
which provides per-db stats as well as global stats.
Change-Id: I1eba19a3a0210d3127acbad119dfd2918414ff4a
|
|
|
|
Change-Id: Ia5ac6f50e023d7d358d17c661b71c6a5880ec445
|
|
Change-Id: Id53d6432a58006653f4d9ddd6355ae505a5273eb
|
|
/etc/check_mk/mrpe.cfg (Bug #6788)
We used file_line before, but when the some check parameters change, a
new line would be added, leaving the old line there, resulting in two
checks with the same name but with different parameters.
Augeas can handle this better, but it is important to use 'rm' to
remove all old lines with different parameters before adding the
new line.
Change-Id: Iad69dfd20f487a16d372a4f4a4bc53299f9e4a66
|
|
minutes, until we are able to fix the issue with the test users creating db bloat.
|
|
systems by default (#6664)
Change-Id: Ic2d4416b7c55f00f01d4b2ade78339d653bc8993
|
|
Change-Id: I0149ac2e767531d9724b57b9e3bdae7943f954ff
|
|
Bug/6566
See merge request !19
|
|
Change-Id: I0d30afbcc6dcb90c6716f7c6bb0bca3e6ae0964a
|
|
Change-Id: I1d8cedfeb1153312c13f7f182c7ac3b031647dd4
|
|
Change-Id: I6d3fa5028ba6eaca7b21a7e850136ef980f6e782
|
|
In order to assure tapicero is still working, we need to monitor
/var/log/syslog for the last tapicero log msg, which should not be older
than the last check_mk_agent run (every 2 mins atm).
|
|
Conflicts:
puppet/modules/site_check_mk/files/agent/logwatch/bigcouch.cfg
Change-Id: I1646e49ffa5437a861b402b755bc15943c42ec4f
|
|
Change-Id: I73defd7964501e4eabe7dd05c02887e7aeb2f063
|
|
Bug/6545
See merge request !16
|
|
Change-Id: I0abeb88f7b6548e5742bd3d99b2f4e5d9c6cf421
|
|
Change-Id: Ie51fb485bcae9a9467c465bdd1b4a5785023db04
|
|
caught (#6540)
Change-Id: I1fe8d4cf60532dfe01cfb3a014c4cbeb4acdc479
|
|
tapicero[921]: Checking security of user-1b3b1fb78db851190fa72dac01207b8d failed (trying again soon): RestClient::ResourceNotFound: 404 Resource Not Found: {"error":"not_found","reason":"Database does not exist."}")
tapicero recovers from this error
Change-Id: Ic105823ddc282512000e6d7445539428581eb997
|
|
Change-Id: I10ec569821f329e3bd10ac87242db102e9c82246
|
|
6539 increase time between check mk agent runs
https://leap.se/code/issues/6539
See merge request !11
|
|
right now, check_mk_agent is run every minute on each host.
The soledad sync test depends on tapicero, and in between finishing the
soledad test and removing the testuser db, and the start of another test
there's only 13s
Change-Id: I5b22ba02470cce799a12043d21091c0c9b8e0b5f
|
|
Change-Id: I198c5245c7e73d6dd7a7d9725fac1eb9a8f425a5
|
|
requirement in logwatch, remove extended regexp character class and also
ignore "Writing security" lines
Change-Id: I7d33725db06a40361a3b04f9591adeb6a025bf77
|
|
Bug/6512
See merge request !5
|
|
Change-Id: I0939070482fad4f99f03e41094a3df42ff5063e4
|
|
Change-Id: I03842b65329aabb012cc2c7514007e174cbd8fc0
|
|
Change-Id: I0b1eec11a3b3da39d65572b6bee8b3ce892e08ac
|
|
now (Bug #6489)
Change-Id: Iaec748a173b6e11bb3ab3c11ca152809817644f9
|
|
environment's contact email (Bug #6466)" into develop
|
|
contact email (Bug #6466)
Change-Id: Ib86ae771e0ac3b6f329a517a8a31c9ec54d33a05
|
|
users (Feature #6481)
There are potentially many tapicero daemons running, and they all try
to do the same thing at the same time. It is basically designed to
create race conditions. All tapicero daemons try to create the user db
at the same time. Only one of them wins the race and actually creates
it.
We need to fix this later (see https://leap.se/code/issues/6480) but
for now, we ignore them because conflict errors should be handled by the
applictation anyway.
Change-Id: I91095b1901d238e3d199954ba3716023d3fd49c1
|
|
Change-Id: I2549d781427fffc865c2bdcd1e950d60dad509fd
|
|
sent out on first failed check_mk check (Bug #6461)
Change-Id: I1bd47b3c3d17508488a4db90d74118006d85a03a
|
|
Change-Id: I52e19bbdfcf6576bd9c247d99aace47eb86c8116
|