Over the years my troubleshooting notes ended up everywhere.
OneNote
ticket comments
random markdown files
screenshots
old documentation
During incidents that made finding the right fix slower than it should be.
So I decided to build a small tool for myself.
Bayou FieldOps is a local troubleshooting runbook that lets me quickly search real-world fixes I’ve encountered over time.
The goal was simple: fast access to solutions when something is broken.
Features:
• searchable runbook entries
• works fully offline
• Linux AppImage build
• Windows portable version
• quick navigation between incidents and fixes
Many of the runbooks come from real issues I've run into such as:
- Active Directory trust relationship errors
- account lockouts
- BigFix exit codes
- sync failures
- common Linux service issues
Originally this was just a personal tool to replace scattered notes, but I packaged it so others might find it useful too.
I'm curious how other sysadmins organize troubleshooting knowledge.
Do you keep runbooks, or rely mostly on docs and ticket history?
Feedback is welcome.
https://bayoufinds.com/b/FsmIu
Top comments (0)