From d9a3ff937b28b3aa077047a2a63c829e65b5d3b7 Mon Sep 17 00:00:00 2001 From: mischa Date: Sun, 31 May 2020 16:16:16 +0200 Subject: [PATCH] updated README.html --- README.html | 275 +++++++++++++++++++++++++++++++--------------------- 1 file changed, 165 insertions(+), 110 deletions(-) diff --git a/README.html b/README.html index accc3d4..a22d598 100644 --- a/README.html +++ b/README.html @@ -1,14 +1,32 @@ - -RRDtool looks nicer... - High5! + +RRDtool looks nicer... - OpenBSD Amsterdam - + + + + + + +
+
OpenBSD Amsterdam Logo
+
364 VMs deployed 🐡
+

RRDtool looks nicer...

-

OpenBSD Amsterdam was in search of a lightweight toolset to keep track of resource usage, at a minimum the CPU load generated by the vmm(4)/vmd(8) hosts and the traffic from and to the hosts. A couple of weeks ago we ended up with a workable [MRTG setup]. While it worked, it didn't look very pretty.

+

March 14, 2019

+ +

OpenBSD Amsterdam was in search of a lightweight toolset to keep track of resource usage, at a minimum the CPU load generated by the vmm(4)/vmd(8) hosts and the traffic from and to the hosts. A couple of weeks ago we ended up with a workable MRTG Setup. While it worked, it didn't look very pretty.

In a moment of clarity, we thought about using RRDtool. Heck, why shouldn't we give it a try? From the previous tooling, we already had some required building blocks in place to make MRTG understand the CPU Cores and uptime from OpenBSD.

+

Before we start:

+ +
+# pkg_add rrdtool
+#
+
+

We decided to split the collection of the different OIDs (SNMP Object Identifiers) into three different scripts, which cron(1) calls, from a wrapper script.