Operations should Communicate Close to the Change
Operations should Communicate Close to the Change
Join the DZone community and get the full member experience.
Join For FreeRead why times series is the fastest growing database category.
If you are editing a file, add a comment to the bit you edited stating you did it and when (and if there’s an internal story/ticket reference)
If you are performing maintenance on a system add a note to the motd so people see it when they login. Be specific about what they should expect to see and what, if anything, should NOT be out of the ordinary (services that should still be running).
If you deprecated an old script, make the script dump an error telling the person what happened. Make the script fail to run if it shouldn’t – don’t just expect that people will not run it, they will.
Think about how someone might come in contact with your change and be defensive, they’ll appreciate it.
Source: http://www.opsbs.com/index.php/2011/11/communicate-close-to-the-change/
Learn how to get 20x more performance than Elastic by moving to a Time Series database.
Like This Article? Read More From DZone
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}