Text and logs · Lesson 17 of 38 · 8 minutes

Awk column extraction

Use awk to pull simple columns from logs.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Print first field
Run awk '{print $1}' /var/log/auth.log.
Hint & worked example
Extract whitespace-delimited fields with the supported print patterns.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
awk '{print $1}' /var/log/auth.log
```
Remember: Quote awk programs so shell variable expansion does not consume $1; single quotes are usually appropriate.
2
Print process field
Run awk '{print $5}' /var/log/auth.log.
Hint & worked example
Extract whitespace-delimited fields with the supported print patterns.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
awk '{print $5}' /var/log/auth.log
```
Remember: Quote awk programs so shell variable expansion does not consume $1; single quotes are usually appropriate.
3
Pipe journal to awk
Run journalctl -u ssh | awk '{print $5}'.
Hint & worked example
Read the training journal by unit or a bounded line window. Extract whitespace-delimited fields with the supported print patterns.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
journalctl -u ssh | awk '{print $5}'
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs. Quote awk programs so shell variable expansion does not consume $1; single quotes are usually appropriate.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

awk: Extract whitespace-delimited fields with the supported print patterns.
Quote awk programs so shell variable expansion does not consume $1; single quotes are usually appropriate.
journalctl: Read the training journal by unit or a bounded line window.
A relevant unit and time range are more useful than an unfiltered wall of logs.

Worked example and expected result

$ awk '{print $1}' /var/log/auth.log

May
May
May
May

Exit status: 0. The command completed successfully in the training fixture.

$ awk '{print $5}' /var/log/auth.log

sshd[104]:
sshd[118]:
sudo[126]:
sshd[141]:

Exit status: 0. The command completed successfully in the training fixture.

$ journalctl -u ssh | awk '{print $5}'

sshd[104]:
sshd[118]:
sshd[141]:

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Awk column extraction”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.Quote awk programs so shell variable expansion does not consume $1; single quotes are usually appropriate.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the awk workflow from “Awk column extraction” to another server, what should you do?Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Cut field selection Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual