diff options
Diffstat (limited to 'gemfeed/2021-10-22-defensive-devops.gmi')
| -rw-r--r-- | gemfeed/2021-10-22-defensive-devops.gmi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2021-10-22-defensive-devops.gmi b/gemfeed/2021-10-22-defensive-devops.gmi index 7470bb98..ae0b70cc 100644 --- a/gemfeed/2021-10-22-defensive-devops.gmi +++ b/gemfeed/2021-10-22-defensive-devops.gmi @@ -81,7 +81,7 @@ First, automate it only on one single server and monitor the result closely. At Now, you can add a handful more canary servers to the automation. You should keep close attention to what the automation is doing. You could use a tool like DTail for distributed log file following. At this point, you could also think of deploying a monitoring check (e.g. Icinga) to see whether your script is not terminating abnormally or logging warnings or errors. -=> ./2021-04-22-dtail-the-distributed-log-tail-program DTail - The distributed log tail program +=> ./2021-04-22-dtail-the-distributed-log-tail-program.gmi DTail - The distributed log tail program From there, you could automate the solution on more and more servers. Best, ramp up the automation to a handful of systems, and later to a whole line of servers (e.g. all secondary servers of a given cluster). And afterwards, automate it on all servers. |