In this post we will take a quick look at how we can import dashboards to our Grafana instance
Session slides, scripts and recording from my session at the Runecast Virtual Conference is available
I’m speaking at the Runecast Virtual conference on Tuesday April 7th
I will give a presentation on Performance Monitoring during this years VMworld in Barcelona
This week I have been on a ‘VMUG Tour’ visiting the Norwegian VMUG branches in Oslo, Bergen and Trondheim. Lots of fun was had and it was nice to meet other members of the community
I had the pleasure of giving a talk about how to do monitoring of the vCenter Server during the VMUG Oslo meeting in December. The session was an extension of what I presented during the VMUG meetings in May and the vBrownbag session during VMworld Europe. The demos showed how we can get health status and metrics from a vCenter Server Appliance utilizing the new REST APIs shipped in 6.5 and 6.
As a Service provider we need to have some way of limiting individual VMs from utilizing too much of our shared resources. When it comes to CPU and Memory this is rarely an issue as we try to not over-committing these resources, at least not the Memory. For CPU we closely monitor counters like CPU Ready and Latency to ensure that our VMs will have access to the resources they need.
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 (Save) Disk space One of them is of course, and this is an obvious one, the amount of data and the corresponding disk space needed to store it.