diff options
| author | Paul Buetow <paul@buetow.org> | 2021-10-22 10:09:37 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2021-10-22 10:09:37 +0300 |
| commit | 9efad77826b6cb75474aff5fb02e140adb4c620d (patch) | |
| tree | d9ebd2722cfe22e199e246480dab0860d77c6b24 | |
| parent | 2ee62fb6c0de767b7ba42f9d9dd44768688ab9c8 (diff) | |
Publishing new version
| -rw-r--r-- | gemfeed/2021-10-22-defensive-devops.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2021-10-22-defensive-devops.md b/gemfeed/2021-10-22-defensive-devops.md index 6a74a1fd..d5086f41 100644 --- a/gemfeed/2021-10-22-defensive-devops.md +++ b/gemfeed/2021-10-22-defensive-devops.md @@ -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. -[DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program) +[DTail - The distributed log tail program](./2021-04-22-dtail-the-distributed-log-tail-program.md) 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. |