Catch a request id: req_ then exactly 12 lowercase hex characters (like req_3f9a0c1d2e4b).
Ops⚡⚡⚡⚡⚡
Ops⚡⚡⚡⚡⚡
Catch · 0/5
- req_a1b2c3d4e5f6Target
- req_000000000000Target
- req_abcdefabcdefTarget
- req_3f9a0c1d2e4bTarget
- req_9e8d7c6b5a41Target
Spare · 0 hit
- REQ_3f9a0c1d2e4bInnocent
- req_3f9a0c1d2e4Innocent
- req_3f9a0c1d2e4gInnocent
- req_3f9a0c1d2e4b5Innocent
- rq_3f9a0c1d2e4bInnocent
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.