Phase 1: Foundations

Bash scripting for operational tasks

Beginner ~3 min read
Think of it this way A friendly analogy. Read this if the technical version feels dense. Show Hide

Okay, imagine you love making your favorite lemonade or a peanut butter and jelly sandwich. You know exactly what to do: get the lemon, slice it, squeeze it, add sugar and water, then stir. Or for the sandwich: grab bread, spread peanut butter, add jelly, put slices together. You do these steps in a specific order every single time. It's a sequence of commands you follow to get the delicious result.

Now, computers also have lots of tasks that need to be done in a specific order, repeatedly. Instead of a person having to type out each command like "check system health" or "move this file" every single time, which can be tiring and easy to mess up, we have something called a "Bash script." Think of a Bash script as your super-detailed recipe card for the computer. It's a list of all the exact steps and commands the computer needs to follow, written down perfectly from beginning to end.

So, when a computer needs to "make" something – like checking if all its different parts are working correctly, or tidying up old files, or even preparing a special report – you don't have to manually tell it each individual step. You just give it the "recipe card" (the Bash script), and the computer reads it and executes every instruction in order, all by itself. This means tasks that used to take a long time and lots of button presses can now be done in a blink, perfectly every time, just by running one simple command that tells the computer to "follow this recipe."

For grown-ups called Site Reliability Engineers (SREs), who are like the chefs managing huge kitchens of computers that run websites and apps for everyone, these "recipe cards" are super important. They use Bash scripts to automatically monitor if a website is serving up its information correctly, to quickly clean up any digital "mess" (like old log files), or even to troubleshoot if something goes wrong. This means you can build your own special recipe books to make your computer do all sorts of helpful chores and checks automatically, keeping everything running smoothly and reliably without you having to do all the fiddly steps yourself.

Bash scripting is a foundational skill for Site Reliability Engineers (SREs) because it's the primary way to interact with and automate tasks on Linux/Unix systems, which form the backbone of most infrastructure. At its core, a Bash script is a series of commands that you would normally type into your terminal, but saved in a file to be executed sequentially. This allows you to automate repetitive operational tasks, such as monitoring system health, managing files, processing logs, and performing routine configuration checks or backups, making your work more efficient and less prone to manual error.

For an SRE, Bash scripting isn't just about running commands; it's about programmatically controlling your server environment. You can use it to quickly diagnose issues by extracting specific information from logs, check the status of services, manage user accounts, or even orchestrate a sequence of actions like stopping a service, applying an update, and then restarting it. Its power lies in its ubiquity and its ability to glue together different command-line tools and utilities that are readily available on any Linux server, providing a rapid solution for immediate operational needs.

While more complex automation might involve languages like Python or Go, Bash often serves as the initial layer for quick automation and daily operational chores. Mastering Bash scripting allows you to gain immediate control over your infrastructure, troubleshoot problems faster, and implement simple yet effective automation without the overhead of compiling or installing extensive dependencies. It's an indispensable tool for maintaining system stability and ensuring operational excellence, forming a crucial part of an SRE's toolkit for managing infrastructure at scale.

Key Takeaways

  • Bash scripts automate repetitive command-line tasks on Linux/Unix systems.
  • Essential for SREs to monitor, manage, and troubleshoot infrastructure efficiently.
  • Used for practical tasks like log analysis, system health checks, and basic service management.
  • Acts as a 'glue' language, orchestrating various command-line tools and utilities.

Code Example

bash
#!/bin/bash

# Script to check disk usage on the root partition and report if it's above a threshold.

THRESHOLD=80 # Set your warning threshold for disk usage percentage

# Get the disk usage percentage for the root partition ('/')
# df -h gives human-readable format
# awk 'NR==2 {print $5}' extracts the 5th column (usage %) from the second line (root partition)
# sed 's/%//' removes the '%' sign for numerical comparison
DISK_USAGE=$(df -h / | awk 'NR==2 {print $5}' | sed 's/%//')

# Compare current usage with the threshold
if [ "$DISK_USAGE" -gt "$THRESHOLD" ]; then
  echo "ALERT: Disk usage on / is at ${DISK_USAGE}% which is above ${THRESHOLD}%!"
  # In a real scenario, you might trigger an alert system here (e.g., send an email, Slack message)
else
  echo "INFO: Disk usage on / is at ${DISK_USAGE}%. All clear."
fi

How this code works

This script automates a fundamental SRE task: monitoring disk usage on the root partition (/) and alerting if it exceeds a set limit. It helps prevent critical system issues caused by full disks, ensuring services remain operational. The script first defines a THRESHOLD variable, typically set to 80 for an 80% usage warning.

The core logic resides in calculating DISK_USAGE. The df -h / command retrieves human-readable disk info for the root partition. This output is then piped to awk 'NR==2 {print $5}', which precisely extracts the percentage value from the second line and fifth column. A subtle but vital step follows: sed 's/%//' removes the percentage symbol. This conversion from "85%" to "85" is essential because the if [ ... -gt ... ] conditional requires a pure numerical value for comparison; otherwise, Bash would report an error. Finally, the script uses an if statement to compare "$DISK_USAGE" against "$THRESHOLD", printing an "ALERT" or "INFO" message accordingly, displaying the current usage with the ${DISK_USAGE}% syntax.

Resources

Related Articles

Hand-picked reads to go deeper on programming for sre.

Back to Site Reliability Engineer Roadmap