From 89f83d49ad7d4cd8baa815993d3172ca72e5b30e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 8 Apr 2023 12:32:25 +0300 Subject: Update content for html --- gemfeed/2021-10-22-defensive-devops.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'gemfeed/2021-10-22-defensive-devops.html') diff --git a/gemfeed/2021-10-22-defensive-devops.html b/gemfeed/2021-10-22-defensive-devops.html index dde46c5a..fc8c914d 100644 --- a/gemfeed/2021-10-22-defensive-devops.html +++ b/gemfeed/2021-10-22-defensive-devops.html @@ -10,7 +10,7 @@

Defensive DevOps



-Published at 2021-10-22T10:02:46+03:00
+Published at 2021-10-22T10:02:46+03:00

                                                             c=====e
@@ -93,7 +93,7 @@
 

 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

+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.

 

@@ -113,7 +113,7 @@
 

 E-Mail your comments to hi@paul.cyou :-)

 

-Back to the main site

+Back to the main site

 

 Generated with Gemtexter |
 served by OpenBSD/httpd(8) |
-- 
cgit v1.2.3