<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>V3.10.2 on blog.monitoring-plugins.pro</title>
    <link>https://blog.monitoring-plugins.pro/tags/v3.10.2/</link>
    <description>Recent content in V3.10.2 on blog.monitoring-plugins.pro</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 17 Feb 2018 18:39:52 +0000</lastBuildDate>
    <atom:link href="https://blog.monitoring-plugins.pro/tags/v3.10.2/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Update function and Grafana compatibility</title>
      <link>https://blog.monitoring-plugins.pro/posts/update-function-and-grafana-compatibility/</link>
      <pubDate>Sat, 17 Feb 2018 18:39:52 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/update-function-and-grafana-compatibility/</guid>
      <description>&lt;p&gt;I can recommend the unstable release &lt;strong&gt;3.10.1_10&lt;/strong&gt; to all experimenting monitoring admins. Above all, this has the character of a technology preview. Included are two major innovations:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The update mode for all getters&lt;/li&gt;&#xA;&lt;li&gt;The option to output Grafana compatible performance data even for status checks.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;update-mode&#34;&gt;Update Mode&lt;/h2&gt;&#xA;&lt;p&gt;The update mode for the getter is quickly explained: adding the option &amp;ndash;update and an age, the getter is instructed to check the existing store first to its age before contacting the filer. Example:```&#xA;$ ./get_netapp_cm.pl -H filer -o volume &amp;ndash;update=3min&#xA;Data for object &amp;lsquo;volume&amp;rsquo; collected within 0.576s. Number of instances stored: 6&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
