Hosting Operations
Read-onlyMap Recent Release Commits
You need to see which tagged release commits exist before choosing a rollback target.
Command
git log --oneline --decorate --graph --all -8Before you run this
System impact: Read-only. Low when scoped to the shown target.
When not to use it: Do not rely on commit order alone when your deploy system can point at a different artifact or symlink.
Expected output
A compact commit graph showing release-2026-06-25-1030 and earlier release tags.
System impact
Read-only. Nothing changes. Git prints the recent commit graph with tags.
Recovery / rollback: no state is changed.
When to use it
Use during rollback planning when you need the shape of recent releases quickly.
When not to use it
Do not rely on commit order alone when your deploy system can point at a different artifact or symlink.
next steps
Related commands
Revert the Suspect Release Commit
Undo a bad release with a new commit instead of rewriting history.
git restore -- app/config.yml && git revert --no-edit release-2026-06-25-1030
Preview the Patch a Rollback Would Apply
Show the exact file changes before moving the branch back.
git diff --stat HEAD..release-2026-06-25-1000
Find a Discarded Commit in Reflog
A reset does not mean the commit vanished.
git reflog --date=iso --format='%h %gd %gs' -6
Find Unusually Large Web Responses
A few huge responses can explain bandwidth, latency, and suspicious download patterns.
awk '$10 ~ /^[0-9]+$/ && $10 > 1000000 {print $10, $1, $7, $9}' /var/log/nginx/access.log | sort -nr | head
Group Server Errors by URL Path
A 500 spike is easier to triage when the broken path is obvious.
awk '$9 ~ /^5/ {count[$7]++} END {for (path in count) print count[path], path}' /var/log/nginx/access.log | sort -nr | head
Study mapping
Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.