<?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: New Splunk Metrics logging interval in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705329#M10339</link>
    <description>&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705328/highlight/true#M10338" target="_blank"&gt;https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705328/highlight/true#M10338&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Nov 2024 22:32:11 GMT</pubDate>
    <dc:creator>hrawat</dc:creator>
    <dc:date>2024-11-26T22:32:11Z</dc:date>
    <item>
      <title>New Splunk Metrics logging interval</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/690321#M10093</link>
      <description>&lt;P&gt;Starting 9.2.0 release&lt;SPAN&gt;&amp;nbsp;internal metrics log event generation can be controlled by group or subgroup.&amp;nbsp; If there are thousands of forwarders,&amp;nbsp; &lt;EM&gt;_internal&lt;/EM&gt; index becomes the most active index and generates lot of hot buckets.&lt;BR /&gt;9.2.0 provides ability to control each metrics group/subgroup.&lt;BR /&gt;&lt;BR /&gt;checkout &lt;EM&gt;`interval`&lt;/EM&gt;&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/limitsconf" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/limitsconf&lt;/A&gt;&amp;nbsp;for more details.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Upon splunk start, metrics.log will log all the controllable metrics groups/subgroups.&amp;nbsp;&lt;BR /&gt;Example metrics.log.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;06-08-2024 03:14:49.659 +0000 INFO  Metrics - Will log metrics_module=dutycycle:ingest at metrics_interval=30.000.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;EM&gt;metrics_module&amp;nbsp;&lt;/EM&gt;is the controllable module logged in metrics.log.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;EM&gt;dutycycle:ingest&lt;/EM&gt; is the&amp;nbsp;the controllable module. &lt;EM&gt;dutycycle&lt;/EM&gt; is the metrics group name and &lt;EM&gt;ingest&lt;/EM&gt; is the subgroup name. It's default logging interval is 30 sec.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;06-08-2024 03:14:49.703 +0000 INFO  Metrics - Will log metrics_module=tailingprocessor:tailreader0 at metrics_interval=60.000.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;tailingprocessor&lt;/EM&gt; is the group name and &lt;EM&gt;tailreader0&lt;/EM&gt; is the subgroup name( where trailing `0` is the first pipeline number).&amp;nbsp;&lt;SPAN&gt;It's default logging interval is 60 sec.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;New metrics logging framework has global default metrics logging interval 60 sec in limits.conf with exception for some modules(30 sec) you will find in metrics.log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[metrics]
interval = &amp;lt;integer&amp;gt;
* Number of seconds between logging splunkd metrics to metrics.log.
* Minimum of 10.
* Default (Splunk Enterprise): 60
* Default (Splunk Universal Forwarder): 60&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;There are so many modules you will find in metrics.log that are never queried. For example &lt;EM&gt;queue&lt;/EM&gt; and &lt;EM&gt;thruput&lt;/EM&gt;&amp;nbsp;metrics is probably the most queried metrics but not necessarily others.&lt;BR /&gt;&lt;BR /&gt;You can increase global default to 120 second&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[metrics]
interval=120&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Customize logging interval for other very critical metrics groups.&lt;BR /&gt;Example there are various `queue` metrics logging. Some are always checked, some rarely.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;06-08-2024 03:14:49.603 +0000 INFO  Metrics - Will log metrics_module=queue:parsingqueue at metrics_interval=30.000.
06-08-2024 03:14:49.663 +0000 INFO  Metrics - Will log metrics_module=queue:httpinputq at metrics_interval=30.000.
06-08-2024 03:14:49.651 +0000 INFO  Metrics - Will log metrics_module=queue:stashparsing at metrics_interval=30.000.
06-08-2024 03:14:49.603 +0000 INFO  Metrics - Will log metrics_module=queue:teequeue at metrics_interval=30.000.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;You can set global default for &lt;EM&gt;queue&lt;/EM&gt;&amp;nbsp;group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[queue]
interval=60&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;parsing 30 sec.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[queue:parsingqueue]
interval=30&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;stashparsing 150 sec.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[queue:stashparsing]
interval=150&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;Interval can be set for [&amp;lt;group&amp;gt;] or [&amp;lt;group&amp;gt;:&amp;lt;subgroup&amp;gt;].&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 21:20:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/690321#M10093</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2024-11-26T21:20:27Z</dc:date>
    </item>
    <item>
      <title>Re: New Splunk Metrics logging interval</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/693183#M10169</link>
      <description>&lt;P&gt;Why isn't it listed under "What's new"?&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.2/ReleaseNotes/MeetSplunk" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.2.2/ReleaseNotes/MeetSplunk&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 12:01:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/693183#M10169</guid>
      <dc:creator>psla</dc:creator>
      <dc:date>2024-07-12T12:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: New Splunk Metrics logging interval</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705328#M10338</link>
      <description>&lt;P&gt;Not one of the&amp;nbsp;change to qualify as new, as it's rather an improvement.&lt;BR /&gt;&lt;BR /&gt;It's documented in limits.conf.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;interval = &amp;lt;integer&amp;gt;
* Number of seconds between logging splunkd metrics to metrics.log
  for different subgroups.
* Check metrics.log for the list of configurable "metrics_modules".
* Set "interval" under the desired "metrics_module" stanza.
* Example:
  * If you want 60 seconds metrics logging interval for "thruput:thruput",
    * [thruput:thruput]
    * interval = 60
* Minimum value is 10 seconds.
* Valid value is multiple of 10.
* If value is not exact multiple of 10, it will be adjusted to nearest
  downward multiple.
* Recommended value multiple of 30. Splunk will decide how often to check for
  metrics reporting based on greatest common divisor across different values.
  If "interval" is set 30, 40 for two different components, then
  greatest common divisor for 30, 40 and 60(default) is 10. It's expensive
  for metrics reporting thread to log every 10 sec.
  If "interval" is set 30, 900 for two different components, then
  greatest common divisor for 30, 90 and 60(default) is 30. It's less
  expensive for metrics reporting thread to log every 30 sec.
* Default : "interval" config value set under [metrics] stanza.&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/limitsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/limitsconf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 21:18:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705328#M10338</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2024-11-26T21:18:48Z</dc:date>
    </item>
    <item>
      <title>Re: New Splunk Metrics logging interval</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705329#M10339</link>
      <description>&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705328/highlight/true#M10338" target="_blank"&gt;https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705328/highlight/true#M10338&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 22:32:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/New-Splunk-Metrics-logging-interval/m-p/705329#M10339</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2024-11-26T22:32:11Z</dc:date>
    </item>
  </channel>
</rss>

