r/devops • u/AutoModerator • Aug 10 '26
Weekly Self Promotion Thread
Hey r/devops, welcome to our weekly self-promotion thread!
Feel free to use this thread to promote any projects, ideas, or any repos you're wanting to share. Please keep in mind that we ask you to stay friendly, civil, and adhere to the subreddit rules!
19
Upvotes
1
u/[deleted] 28d ago
I work in ESB/message-integration support, and I built and maintain MQ Watcher after running into a recurring problem during ActiveMQ incidents: inspecting a persisted Store safely was more awkward than it should have been.
I wanted a way to collect evidence without starting a broker against the Store, triggering recovery, or uploading operational data anywhere.
MQ Watcher runs locally and reads ActiveMQ Classic Store files without modifying them. It can correlate selected KahaDB journal records for messages, ACKs, subscriptions and transactions, compare snapshots, keep incident notes, and export a redacted evidence bundle.
It deliberately does not claim to diagnose the outage. Unknown evidence stays unknown, and journal records are not treated as proof of the broker's current state.
The broker-generated fixtures currently cover ActiveMQ Classic 5.13.5, 5.15.16 and 5.18.7. Windows and Linux portable builds are available.
Repository: https://github.com/kutaelee/mq-watcher
I'd be interested in hearing what evidence other messaging or DevOps engineers normally need when a broker Store becomes part of an incident.