<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why is the collectd interval not working? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-collectd-interval-not-working/m-p/413714#M94050</link>
    <description>&lt;P&gt;MuS, thanks for replying! You are correct, it's not directly a splunk question, but since it is the suggested way to get linux metrics into splunk, I thought I'd ask here.&lt;/P&gt;

&lt;P&gt;On RHEL 7.5 running collectd 5.8.0, collectd -t and collectd -T return fine. -h tells me the default config file is /etc/collectd.conf&lt;/P&gt;

&lt;P&gt;I've looked at that bug you linked, so I un-commented the interval line in /etc/collectd.conf, and set it to 300. (As it is set to 10 by default)&lt;/P&gt;

&lt;P&gt;I've grep'd Interval in /etc/collectd.conf and /etc/collectd.d/* and looked for any other Interval settings that could override it, and there aren't any.&lt;/P&gt;

&lt;P&gt;I do know it's using the correct config file, because all of my plugins are being loaded!&lt;/P&gt;

&lt;P&gt;I'm leaning towards it's a bug in RedHat's release of collectd. I've got a ticket open with them. I'll update here.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Oct 2018 19:48:57 GMT</pubDate>
    <dc:creator>jamessevenerlmc</dc:creator>
    <dc:date>2018-10-10T19:48:57Z</dc:date>
    <item>
      <title>Why is the collectd interval not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-collectd-interval-not-working/m-p/413712#M94048</link>
      <description>&lt;P&gt;I'm working on a solution to send metrics from a number of Linux servers running RHEL 7.5.&lt;/P&gt;

&lt;P&gt;I've got collectd installed and sending data via an Http Event Collector. The issue is that no matter where I set the Interval setting, I'm still seeing metrics written every 10 seconds (the default according to &lt;A href="https://collectd.org/documentation/manpages/collectd.conf.5.shtml#synopsis"&gt;https://collectd.org/documentation/manpages/collectd.conf.5.shtml#synopsis&lt;/A&gt;)&lt;/P&gt;

&lt;P&gt;Has anyone run into this? I'm looking to set Interval to 300 seconds.&lt;/P&gt;

&lt;P&gt;Interval 300 in /etc/collectd.conf and /etc/collectd.d/myApp.conf haven't done anything.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Oct 2018 16:00:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-collectd-interval-not-working/m-p/413712#M94048</guid>
      <dc:creator>jamessevenerlmc</dc:creator>
      <dc:date>2018-10-10T16:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the collectd interval not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-collectd-interval-not-working/m-p/413713#M94049</link>
      <description>&lt;P&gt;Hi jamessevenerlmco,&lt;/P&gt;

&lt;P&gt;I don't see how this can be a Splunk question &lt;CODE&gt;¯\_(ツ)_/¯&lt;/CODE&gt; but since you got my attention .... here we go &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;You are right in setting the &lt;CODE&gt;Interval&lt;/CODE&gt; option, remember it can be set globally or per plugin. &lt;BR /&gt;
Have to run &lt;CODE&gt;collectd -t&lt;/CODE&gt; to test your config and more important have you run &lt;CODE&gt;collectd -h&lt;/CODE&gt; to get the information about the default config file location?&lt;/P&gt;

&lt;P&gt;Because running it with collectd 5.7.1 tells me the default location of the config file is &lt;CODE&gt;/etc/collectd/collectd.conf&lt;/CODE&gt; not &lt;CODE&gt;/etc/collectd.conf&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Maybe this can helps as well &lt;A href="https://github.com/collectd/collectd/issues/2444"&gt;https://github.com/collectd/collectd/issues/2444&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;If this all does not help you can always strace the pid and see which config file it really loads.&lt;/P&gt;

&lt;P&gt;hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS &lt;/P&gt;</description>
      <pubDate>Wed, 10 Oct 2018 19:17:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-collectd-interval-not-working/m-p/413713#M94049</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2018-10-10T19:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the collectd interval not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-collectd-interval-not-working/m-p/413714#M94050</link>
      <description>&lt;P&gt;MuS, thanks for replying! You are correct, it's not directly a splunk question, but since it is the suggested way to get linux metrics into splunk, I thought I'd ask here.&lt;/P&gt;

&lt;P&gt;On RHEL 7.5 running collectd 5.8.0, collectd -t and collectd -T return fine. -h tells me the default config file is /etc/collectd.conf&lt;/P&gt;

&lt;P&gt;I've looked at that bug you linked, so I un-commented the interval line in /etc/collectd.conf, and set it to 300. (As it is set to 10 by default)&lt;/P&gt;

&lt;P&gt;I've grep'd Interval in /etc/collectd.conf and /etc/collectd.d/* and looked for any other Interval settings that could override it, and there aren't any.&lt;/P&gt;

&lt;P&gt;I do know it's using the correct config file, because all of my plugins are being loaded!&lt;/P&gt;

&lt;P&gt;I'm leaning towards it's a bug in RedHat's release of collectd. I've got a ticket open with them. I'll update here.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Oct 2018 19:48:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-collectd-interval-not-working/m-p/413714#M94050</guid>
      <dc:creator>jamessevenerlmc</dc:creator>
      <dc:date>2018-10-10T19:48:57Z</dc:date>
    </item>
  </channel>
</rss>

