svn commit: r51427 - head/en_US.ISO8859-1/htdocs/news/status

Sun Feb 18 00:29:39 UTC 2018

Author: bjk
Date: Sun Feb 18 00:29:38 2018
New Revision: 51427
URL: https://svnweb.freebsd.org/changeset/doc/51427

Log:
  Add 2017Q4 LibreNMS ZFS reporting entry from Zane Bowers-Hadley

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2017-10-2017-12.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-10-2017-12.xml
==============================================================================

--- head/en_US.ISO8859-1/htdocs/news/status/report-2017-10-2017-12.xml	Fri Feb 16 19:08:42 2018	(r51426)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-10-2017-12.xml	Sun Feb 18 00:29:38 2018	(r51427)
@@ -120,4 +120,80 @@
       veracity of any claims in these submissions.</p>
   </category>
 
+  <project cat='misc'>
+    <title>LibreNMS</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Zane</given>
+	  <common>Bowers-Hadley</common>
+	</name>
+	<email>vvelox at vvelox.net</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://github.com/librenms/librenms/pull/7938">LibreNMS ZFS Addition</url>
+    </links>
+
+    <body>
+      <p>LibreNMS is an autodiscovering PHP/MySQL/SNMP-based network
+	monitoring solution which includes support for a wide range of
+	network hardware and operating systems, including Cisco,
+	Linux, &os;, Juniper, Brocade, Foundry, HP and many more.</p>
+
+      <p>Among other things, it can monitor applications and other
+	functionality running on a server via SNMP extensions.  This
+	has been the area of focus for my present work.</p>
+
+      <p>ZFS support has been committed towards the end of December,
+	which was too late to make the December release, but it will
+	be in the January release.</p>
+
+      <p>This brings the ability to monitor ARC and pool information,
+	with each pool having its own separate set of graphs.</p>
+
+      <p>The ARC graphing is as below.</p>
+
+      <ul>
+	<li>ARC size in bytes</li>
+
+	<li>ARC size, percent of max size</li>
+
+	<li>ARC size breakdown</li>
+
+	<li>ARC efficiency</li>
+
+	<li>ARC cache hits by list</li>
+
+	<li>ARC cache hits by type</li>
+
+	<li>ARC cache misses by type</li>
+
+	<li>ARC cache hits</li>
+
+	<li>ARC cache misses</li>
+
+	<li>ARC misc (deleted, skips, and recycle misses)</li>
+      </ul>
+
+      <p>The pool tracking is comparatively much simpler, using the
+	output from <tt>zpool list</tt>.</p>
+
+      <ul>
+	<li>Pool Space</li>
+
+	<li>Pool Capacity</li>
+
+	<li>Pool Fragmentation</li>
+      </ul>
+    </body>
+
+    <help>
+      <task>Suggestions are needed for additional statistics or other
+	information to monitor, whether &os;-specific or
+	otherwise.</task>
+    </help>
+  </project>
 </report>
