A side effect of setting up your own VMWare lab is that, after all is said and done, you end up with a little furnace in a closet. With Orlando weather, this is mostly unnecessary.
Having recently setup the ELK stack to monitor this VM, I searched for the string ‘temperature’ not knowing what I would find.
Bingo, the image above clearly shows temperature warnings from the three hard drives in VM.
I recently bought a cheap Arduino Board on eBay that came with a CH34x USB to Serial Chip. The eBay seller offered a link and instructions for the drivers for Linux, Mac and Windows. Installing/loading this in Crouton was not straightforward however.
Connecting the board and opening ide shows the lack of connection as expected. Note the grayed-out ‘Port’ Selector.
Cool and quick dabble on Kibana4 for custom color palettes. Since Kibana4 is the blaze of the future and old Kibana is not coming back, its worth our time spending time getting to know this latest version.
Here is neat ‘temp graph’ using a custom color palette and temperature data from drives in pc.
And here is the original for reference.
Monitor anything; this is what fills your head after playing with Elasticsearch, Logstash and Kibana.
ELK Stack, meet VMWare Server. Since VMWare’s ESXi runs on some Linux kernel, it shares the logging facilities we’re familiar with on Linux systems. Going about forwarding syslog messages to a remote box is a bit different thou. Luckily, VMWare’s Knowledge Base is very thorough if you know where to look.
So last night I found this on my lab machine…
Silly node ran out of space. Spawning up extra node promptly made this a non-issue.
It is so nice to work with open source tools built to handle failure gracefully. A few years ago the above scenario would have prompted a weekend-at-the-colo to the dismay of family and my sanity. These are interesting times!
- First time running with a pacer. Way to go Kristen.
- First time racing with Polar! M400 ftw.
- Running in the dark for the first few miles. Street lamps had lots of style but gave but a nice glow that didn’t light road.
- Half marathon may be sweet spot. Not too long not too short.
- A big portion of course was out-and-back along Tampa Bay. This gave us, the slow runners, a clear view of the elites on their way back to finish line. It was breathtaking to see the game these runners are playing. Lets just say that their stride looks very different than mine. Wow, I’m looking up!
- Include water stations in training/race strategy. I usually walk the stations and had to play catch-up to pace group. Every, single, time. Goodness, they can drink and run at the same time.
- Review course, at least on map. Right after mile 12, an awesome person on a crane overhead us runners blasted ‘finish-line after bridge’ over megaphone. Jolt of excitement goes thru my body, which is starting to ache. I kind off see bridge in the distance. Off I go, empty my cup! Finnish line was after SECOND bridge. Thanks dude… I almost did my dance 200 ft from the finish line.
- Plan breakfast ahead of time. It’s about impossible to wing breakfast at 4am. Ran on empty stomach and just about fainted an hour after run.
- Plan post-race reunion with loved ones ahead of time. Winged this and it caused unnecessary aches (and extra walking).
Best race yet. I would definitely consider revisiting Tampa next year for Gasparilla Half.
In this post, I am will be go over using the Collectd input on Logstash for gathering hardware metrics. For Logstash output, I am going to be using Elastcisearch. Logstash will allow us to centralize metrics from multiple computers into Elasticsearch. On top of Elasticsearch, I am using going to be using Kibana to display these metrics.
To this Kibana dashboard, we could add additional metrics for the processes taxing the system being monitored. This would effectively show a cause and effect story in one integrated dashboard.