Recently there was a new release of Telegraf, a monitoring agent from the guys that built InfluxDB. This new version, 1.8.0, comes with a plugin for vSphere which I’m pretty excited about!
Previously I’ve been testing Telegraf for monitoring some Linux VMs and also my InfluxDB servers and the agent works as expected and it’s as easy to use as the other products in the TICK stack from Influx.
If you’ve followed my blog series about building a monitoring solution for vSphere and other infrastructure components you know that I’ve pulled metrics with PowerCLI scripts. With this new plugin to Telegraf I want to see if I can use this as a replacement. ...
The schedule builder for VMworld Europe 2018 in Barcelona is finally live and sessions can be scheduled.
For the first time I will have a session at VMworld, as one of the vBrownBag/VMTN community sessions, and I’m really excited about this.
It is very cool that these community sessions are available in the schedule builder and can be scheduled as other sessions. My session is: ...
For a long time, actually since we migrated to the VCSA in 6.5 last year, I’ve wanted to utilize the REST API in the appliance to have some monitoring of them.
For several reasons I’ve had to put that on hold, one of them being that there seems to be something wrong with the back-end authentication calls. I get authentication errors on certain calls no matter which user I am logged in with (also the vsphere.local admin account).
"default_message": "Unable to authenticate user",
I had the privilege of delivering 3 sessions at VMUG Norway this week in Oslo, Trondheim and Bergen.
With the extremely nice weather in Norway this week in mind the attendance were great and as always the discussions were valuable.
My session on vSphere Performance monitoring were the short version of the blog series I did about how we built our solution for doing performance monitoring of vSphere with InfluxDB and Grafana, and how we easily can customize with adding metrics and datasources. ...
I’ll be speaking at VMUG Norway’s meetings this May.
As always there will be “three sessions in three cities”.
- Oslo, May 29th
- Trondheim, May 30th
- Bergen, May 31st
The topic for my session will be how we have built our own vSphere Performance monitoring solution which I’ve also done a blog series about. ...
At work I have done some monitoring projects which I’ve done many blog posts about. At home I have a small vSphere environment serving partially as a Lab but it also runs some services we use at home. Of course I do monitoring of this environment as well, and I use both InfluxDB and Grafana as we do at work.
One of my VMs runs Plex Media Server and recently I moved my media library to a separate box running FreeNAS. I’ve used FreeNAS as a part of my lab earlier as an ISCSI target and serving storage for VMs, but it’s now only serving my media files to the Plex VM.
The FreeNAS has it’s own performance monitoring available through the Web GUI, but of course I have wanted to incorporate it in my own monitoring solution. I’m not very familiar with the FreeBSD OS which FreeNAS runs on, and I wasn’t very keen on installing any agents on it. ...
In my blog series on building a solution for monitoring vSphere Performance we have scripts for pulling VM and Host performance. I did some changes to those recently, mainly by adding some more metrics for instance for VDI hosts.
This post will be about how we included our VSAN environments to the performance monitoring. This has gotten a great deal easier after the Get-VSANStat cmdlet came along in recent versions of PowerCLI.
For those of you that have read my blog you probably know I’ve done a series on performance monitoring infrastructure with the help of InfluxDB.
InfluxDB is a part of the TICK stack delivered by InfluxData. All components are open-sourced and available. The TICK stack consists of, Telegraf, InfluxDB, Chronograf and Kapacitor.
This post will do a quick review and some examples on how I have started exploring them in my Performance monitoring project. ...
If you’ve followed my vSphere performance data blog series you probably have noted that I used InfluxDB as the database for storing the performance data.
With over 4 months of performance data in the InfluxDB I’ve picked up some gotcha’s along the way (there’s probably more lying around which I’ve not come over yet).
In this blog post I’ll outline what I’ve learned so far ...