commit d9a3ff937b28b3aa077047a2a63c829e65b5d3b7 from: mischa date: Sun May 31 14:16:16 2020 UTC updated README.html commit - 7c02cf83d68d74da6637dec4b5aa5e17dd4c38b2 commit + d9a3ff937b28b3aa077047a2a63c829e65b5d3b7 blob - accc3d4e805c6a62f6326571027815fc8ef17cc7 blob + a22d598bd6d922196619ff31e16cd2b1e78ae359 --- README.html +++ README.html @@ -1,14 +1,32 @@ - -RRDtool looks nicer... - High5! + +RRDtool looks nicer... - OpenBSD Amsterdam - + + + + + + +
+
OpenBSD Amsterdam Logo
+ +

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.