Catch a stack trace line: at, a space, a function name, a space, then file:line in parentheses (like at main (app.js:12)).
Ops⚡⚡⚡⚡⚡
Ops⚡⚡⚡⚡⚡
Catch · 0/5
· space→ tab- at·go·(main.go:33)Target
- at·load·(index.ts:7)Target
- at·main·(app.js:12)Target
- at·run·(server.py:240)Target
- at·init·(a.js:1)Target
Spare · 0 hit
- at··main·(app.js:12)Innocent
- at·main·(app.js:)Innocent
- main·(app.js:12)Innocent
- at·main·app.js:12Innocent
- at·main·(app.js)Innocent
Your pattern
About this pack
Intermediate · 6 levels
Logs & ops is regex for the strings operations people read all day: request ids, deploy environments, memory sizes, port mappings, stack trace lines and Kubernetes pod names. Exact lengths matter here, so counted repeats like {12} do a lot of the work.
You begin with request ids like req_3f9a0c1d2e4b, with exactly 12 hex characters after the prefix. Then come environments like prod-2, sizes like 16KB and 2GiB, port mappings like 8080:80, trace lines like at main (app.js:12) and pod names like web-7d4b9c8f6-x2k9p.
Every level also has hidden checks: words you don’t see. Passing the words on screen solves a level; passing the hidden checks too ranks it.
The Field work track works through logs and receipts the same way. Money & finance has more formats where one character too many is wrong.