2 minute read

A couple of handy low-level Linux tools included this week for logging and auditing. It’s interesting to see continued improvements on well-worn themes, alongside posts espousing serverless and public cloud.


2016/17 State of On-Call Webinar (with DevOps.com): Register to learn what 800+ survey respondents have to say about life on-call.


A Tale of Two Pipelines: To DevOps or Not to DevOps

Trying to move to a DevOps methodology, or improve your current DevOps methods? Need to increase innovation and the speed of your software delivery pipeline? Brett Hofer, Global DevOps Practice Lead at Dynatrace, will show you how through a tour of two pipelines. You’ll get insights on key pipeline factors that plague traditional delivery pipelines and how to overcome them with practices that establish a true DevOps.


A good exploration of why you probably shouldn’t be focusing your efforts (as an organisation or I’d say as an individual) on build private clouds.

The co-evolution of technical systems and operational practices is a common theme on this newsletter. This post takes a close look at how serverless emerged and why it’s going to be important.

The Linux audit subsystem is pretty great and this post explores some of it’s capabilities and the reasons why you might want to audit syscalls. It also has some interesting discussions about different applicable tools.

An interesting example of wrapping existing application code and packaging it up as a container. In this case talking a COBOL application and allowing you to integrate it into your Docker stack.

Kubernetes is definitely gathering steam, and lots of organisations are looking to provide a Kubernetes distribution. This post explores what this means for the likely consumers.

An exploration of implementing a green/blue deployment scheme for Lambda based serverless applications. No perfect approach yet it seems but some useful ideas.

A quick look at best practices for testing Ansible playbooks on Windows using Test Kitchen.

Logging is an area that can benefit from improvements in most organisations, and this post does a good job of coming to that realisation and then lots of code examples of implementing a robust logging setup.


mtail looks handy for anyone with a set of logs that would like to get that information into a time series database of your choice. A simple DSL for parsing logs and incrementing counters, and sending the data to Prometheus, collectd, StatsD, or Graphite.

Mentioned in one of the posts above, go-audit is a tool for streaming Linux audit events into a centralised monitoring infrastructure, rather than processing the events locally.

2016/17 State of On-Call Webinar (with DevOps.com): Register to learn what 800+ survey respondents have to say about life on-call.