- 14 Feb, 2020 1 commit
-
-
Łukasz Nowak authored
This will lead to minimise amount of entries, and they will be only shown when the status would change.
-
- 12 Feb, 2020 11 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Improvements: * total_seconds from surykatka is parsed * failure-amount is configurable * various smaller bugfixes /reviewed-on !77
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Result of the promise is not important for instantiation.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Sites with bad certificates are reported with null values in surykatka output, thus they have to be handled correctly.
-
Łukasz Nowak authored
It means that the server didn't reply at all.
-
Łukasz Nowak authored
Show URL only once and having this in mind simplify messages still keeping all information.
-
Łukasz Nowak authored
It is only checked when maximum-elapsed-time is passed and surykatka is recent enough to report total_seconds. Also improve reporting even more to provide readable information for those massive promises with ERROR/OK mixed states.
-
Łukasz Nowak authored
Prefix with ERROR and OK messages for problems and ok checks, as they are grouped together in the output.
-
- 29 Jan, 2020 1 commit
-
-
Bryton Lacquement authored
This is another fixup for commit 1c8269b2. This is not covered by tests since they use a fake_send method.
-
- 28 Jan, 2020 1 commit
-
-
Łukasz Nowak authored
-
- 09 Jan, 2020 5 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Additionally improve python3 support as it is required for proper cleanup procedure. /reviewed-on nexedi/slapos.toolbox!74
-
Łukasz Nowak authored
-
Łukasz Nowak authored
The file_list will be iterated more than once, and filter in python3 is being consumed, so create a list instead for many iterations.
-
Łukasz Nowak authored
os.errno does not exists since python 3.7
-
- 02 Jan, 2020 2 commits
-
-
Łukasz Nowak authored
Fixed check_surykatka_json for http-only sites
-
Łukasz Nowak authored
ssl_certificate is not important for http only checks.
-
- 31 Dec, 2019 8 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Improvements: * support for ssl_certificate entry from surykatka * explanation of extended status codes * assurance that URLs are clickable in the monitor.app * format times for humans /reviewed-on nexedi/slapos.toolbox!73
-
Łukasz Nowak authored
-
Łukasz Nowak authored
"Extended" status codes, like 524, 526 and others, come from surykatka itself and shall be amended with additional explanation
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Since standard date format is used in the ssl_certificate checks, do the same for readability and consistency in bot_status.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
-
- 30 Dec, 2019 1 commit
-
-
Julien Muchembled authored
-
- 12 Dec, 2019 2 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
/reviewed-on nexedi/slapos.toolbox!72
-
- 11 Dec, 2019 1 commit
-
-
Thomas Gambier authored
in https://lab.nexedi.com/nexedi/slapos/blob/master/stack/monitor/templates/monitor-httpd.conf.in there is no such thing as `/share/public/` URL /reviewed-on nexedi/slapos.toolbox!71
-
- 10 Dec, 2019 1 commit
-
-
Łukasz Nowak authored
-
- 09 Dec, 2019 1 commit
-
-
Łukasz Nowak authored
As bootstrapMonitor is run many times and each execution takes taime it's better to have the status file there during monitor is running, especially if previous runs were good. This file is used by other tools to check last state of bootstrap monitor, and if it disappears for execution of monitor it can result with false alarms. /reviewed-on nexedi/slapos.toolbox!70
-
- 05 Dec, 2019 3 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Since etc/promise was migrated to etc/plugin a lot of installations are without etc/promise folder, and monitor configuration is without legacy-promise-folder option. /reviewed-on nexedi/slapos.toolbox!69
-
Łukasz Nowak authored
/reviewed-on nexedi/slapos.toolbox!68
-
- 02 Dec, 2019 2 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
There was mistake, as result_max[0] is already free disk space, so there was no need to do 1. - result_max[0]. Unfortunately tests were also incorrectly adjusted.
-