I love Nagios.
I love Raspberry PIs.
It’s awkward to shoehorn Nagios into into an rPi.
Somebody fixed that particular annoyance.
Honestly, this has been around for a few years, but I’ll have to learn something about it and stop trying to hack together my own solutions.
Some summary info is on an older Cat5 Tech TV episode:
We’re using Hubot for very limited automation and integration with our messaging apps. We’ve renamed it from “hubot” to “alfred”.
To make a request, you simply begin with “alfred …” Like, for example, you need it to build a cluster, the instruction might be alfred build <region> <name> Of course, the ‘region’ and ‘name’ are variables that you’ll define when running it. You could even just do alfred help to get a complete list of every defined process that it’s capable of. Really simplistic, honestly.
But the confusion that arises just from the bot’s name is amusing. People mistakenly (accidentally on purpose?) type things like:
albert build us-west-2 devclusteralvin build eu-west-1 myclusteralthea helpalexa do the buildHeh… remember that SNL skit from a couple of years ago? Same thing, really:
Digging around in Jira, I discovered there’s a ticket assigned to me that’s been in progress since October…
…2015. 🤔
**clicks Close**
Yeah, that might skew my numbers. 😁
Yep, it’s kind of been one of those days so far:
That is all.
…if you want things inconsistent.
Automation ensures repeatability.
<rant=begin>
If you have a manual process, that you want to do manually — because reasons — you may be able to do it somewhat identically 10 or 100 or even 10,000 times. But if that process changes (it will), or you get forgetful (you will), or you make a simple mistake (you will), or die (going to happen), then it’s most certainly not repeatable.
Also, a few words on “reasons” — they’re quite often just excuses and justifications for remaining static.
</rant=end>
the rest of me 