I’ve been messing around with compiling Sensu Go for several different platforms lately. In my last post, I got Sensu Go agents running on my Raspberry Pis and Nvidia Jetson Nanos. I wanted to see if I could get an agent running on OS X as well, because who doesn’t want to monitor their laptop! The Setup Similar to what I did previously (and subsequently learned a ton more about), we’ll need to compile the Sensu Go packages since they’re not currently packaged for OS X.
UPDATES When I originally wrote this post, I was operating under some outdated assumptions when it comes to building Sensu on arm devices. I’ll post the updates here at the beginning of the article, and you can read on to see how I’d previously set up Sensu on my Nvidia Jetson Nanos. Compiling Sensu Go As a Go novice, I didn’t fully understand the workflow for compiling Sensu for arm devices.
This past week, I had the pleaseure of attending Dockercon. While I was there primarily working the Sensu booth, it occurred to me that Docker presents an ideal way to demo what Sensu does, and I can quickly get an environment up without having to go through the rigmarole that I previously did using Vagrant. Now, that’s not saying that I think one tool is better than the other, but for the purposes of quick demos, Docker is more useful to me.
I’ve tried quite a few to-do apps. Google Tasks, Todoist, Wunderlist, Any.do, . I’ve even tried using things like a planner, or a Bullet Journal. No app, no physical piece of paper seems to do the trick when it comes to keeping track of things I need to do. That is, until I started using a tool that could emulate a Kanban-style workflow. Let’s start with “What the heck is a Kanban board?
UPDATED I found that there is an exception to what the solution is here, namely that this only applies to VirtualBox 5.2. If you end up using Virtualbox 6.0, note that this won’t work. the longer term fix would be to downgrade your VirtualBox version. ORIGINAL POST I use minikube for a lot of quick troubleshooting and demos. I recently found myself in a situation where the IP address kept incrementing.
It’s been a long time coming, but I’ve finally got the KegPi mostly working and being monitored with Sensu! This post is going to go over the whole kit and caboodle and is going to build on the posts of creating the kegerator and getting Sensu to run on a Raspberry Pi. The deep and dark part of this post will cover: The code to measure the temp/contact sensors (Sensu Plugin) Writing Sensu checks that will incorporate that code Exporting the data from the temp sensor to Graphite and InfluxDB for seeing temperature trends Writing the Plugins If you haven’t had a chance to read the previous post on using Sensu to monitor Raspberry Pis, I’ll give you a short blurb about Sensu.
I’ve met quite a few homebrewers over the years and have learned tons from them. One of the things I always like asking about it their setup and getting to know what they use on brew day. I figured it’s time for me to do a HIB (How I Homebrew) post and let you know what I started brewing on, and where I’ve progressed. For Starters When I first started brewing, I started on a hand-me-down Mr.
Back in August, I took a Customer Success role at Sensu. I’d been familiar with Sensu through my various bits of tinkering and dabbling with monitoring in the past, and was happy to take the role and work with the Sensu team officially. Now that I’ve been working with Sensu for a few months (and am officially on paternity leave for the next several weeks), I decided it was time to revisit the idea of using Sensu to monitor my Kegpi’s various sensors.
I’ve posted previously about homebrewing and have been brewing for almost three years now. Back in April, I took to destroying a perfectly good mini fridge to turn it into a kegerator. As any homebrewer can tell you, bottling is a pain in the ass. The delabling (if you’re reusing bottles), the santization, and the bottle carbonization makes for a rather long and laborious process. Because I’d finally had it with bottling, I decided that kegging would be a wiser choice since:
I’m a bit of a productivity nerd, I’ll admit. Over the last couple of years, I’ve cultivated a workflow that revolved around a lot of OS X tools that I LOVED: Alfred TextExpander iTerm2 These tools were my bread and butter. My professional life, if you will. However, I found myself in a bit of an odd spot in recent months–my MacBook Air was proving to be underpowered for running VM’s, and doing any sort of virtualized anything (which I wanted to be able to do for some training and other projects).