We’re always looking out for new ways to visualize our performance data. Most often to aid our troubleshooting, but sometimes most for fun. This is one of those times. Let’s check out how we can visualize our compute usage across the world!
After moving my blog to the Hugo platform hosted on Netlify I lost the uptime monitoring I had through Jetpack on Wordpress. As I’ve worked quite a bit with Grafana I knew about their Worldping service, but I haven’t had any real need to test it before now. Now I had the perfect reason for checking it out.
Last weekend I completed the preparations for moving this blog from Wordpress to Hugo. I have been considering this a few times, but never really had the time or energy to go the full length. Until now..
HPE launched their InfoSight for servers back in January and as we have been using InfoSight for both Nimble and lately for our 3PAR systems we wanted to bring our compute into the mix as well
A couple of weeks ago I got the exciting news that I was accepted as a VMware vExpert for the second time. This award is a huge achievement for me and I’m humbled to be included in a community with so many top individuals, many of which I have learned so much from over many years
This is a short revisit of an earlier blog post on automating ESXi installation through PXE booting and Kickstart scripts
Late last week I finally got my results from the VCAP DCV deploy exam which I sat mid-December. I was of course extremely pleased to learn I had passed the exam. In this post I will share some of my thoughts on the exam.
HPE recently announced that their HPE InfoSight service now supports servers. This is something we have been waiting for and we’re eager to check out the new functionality
As a follow-up of my exploration of the HPE PDU REST API I wanted to create a Powershell module as a wrapper for the API. I’ve previously written a post on how to create a Powershell module as a wrapper for an API here. The PDU module will be built in the same way where there will be a private function that handles the actual API requests
In a previous post I described how we are setting up remote offices for a customer with two-node vSAN clusters. I meant to get this post out right after that previous one, but things happened… Anyways, here’s how we automated those two-node vSAN clusters. Currently we have 7 of these racks ready with more to come. As these will be installed at distant locations we are extra keen on knowing that they are all configured as they should, and that the configuration is the same cross these multiple locations.
