[01:46:56] <cdanis>	 \o/
[07:49:27] <godog>	 this morning' scratching of head is brought by this UNKNOWN check in icinga
[07:49:33] <godog>	 logstash1008
[07:49:33] <godog>	 
[07:49:33] <godog>	 ElasticSearch unassigned shard check - 9200
[07:49:33] <godog>	 
[07:49:35] <godog>	 UNKNOWN	2019-07-18 23:11:52	0d 8h 35m 56s	1/1	UNKNOWN - HTTPConnectionPool(host='localhost', port=9200): Read timed out. (read timeout=4)
[07:49:43] <godog>	 although
[07:49:44] <godog>	 root@logstash1008:~# /usr/lib/nagios/plugins/check_elasticsearch_unassigned_shards.py --url http://localhost:9200
[07:49:47] <godog>	 OK - All good
[09:22:24] <godog>	 ok retry interval is two hours for the check, forcing again a check "fixed" it
[09:38:38] <jbond42>	 moritzm: yay :D
[09:44:17] <moritzm>	 jbond42: when the package has been uploaded to buster-proposed-updates (a kind of staging repo for the next point release) we should upgrade one of the buster hosts to that version and verify/confirm on the release.debian.org bug that it works fine (always helps if the Debian stable release managers get additional feedback)
[09:44:51] <jbond42>	 yes sounds good to me
[12:53:14] <cdanis>	 godog: it seems to me that we often use retry_interval as a kludge for "should only alert after it has been true for a certain duration"
[12:58:59] <godog>	 cdanis: indeed, and max_check_attempts