<?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 Why are universal forwarders reporting error &amp;quot;Metric with the name thruput:thruput already registered&amp;quot;? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204501#M40359</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;

&lt;P&gt;By examining the _internal logs I found the following, Metric Error:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ERROR Metrics - Metric with name thruput:thruput already registered
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It is reported by Universal Forwarders of several Clients spread over the entire day (with peaks in the morning hours - so I suppose that it's related to the client's start-up)&lt;/P&gt;

&lt;P&gt;The interesting thing is, that all of these clients are still reporting events to the Indexers...&lt;/P&gt;

&lt;P&gt;Questions:&lt;BR /&gt;
Why does this happen?&lt;BR /&gt;
And how can I avoid this?&lt;/P&gt;

&lt;P&gt;thx&lt;/P&gt;</description>
    <pubDate>Tue, 16 Feb 2016 08:04:04 GMT</pubDate>
    <dc:creator>pilzi81</dc:creator>
    <dc:date>2016-02-16T08:04:04Z</dc:date>
    <item>
      <title>Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204501#M40359</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;

&lt;P&gt;By examining the _internal logs I found the following, Metric Error:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ERROR Metrics - Metric with name thruput:thruput already registered
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It is reported by Universal Forwarders of several Clients spread over the entire day (with peaks in the morning hours - so I suppose that it's related to the client's start-up)&lt;/P&gt;

&lt;P&gt;The interesting thing is, that all of these clients are still reporting events to the Indexers...&lt;/P&gt;

&lt;P&gt;Questions:&lt;BR /&gt;
Why does this happen?&lt;BR /&gt;
And how can I avoid this?&lt;/P&gt;

&lt;P&gt;thx&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 08:04:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204501#M40359</guid>
      <dc:creator>pilzi81</dc:creator>
      <dc:date>2016-02-16T08:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204502#M40360</link>
      <description>&lt;P&gt;Sorry for bringing up this old thread but are there any news about this? We ran into the same issue on our UF (version 6.5.0).&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2017 12:53:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204502#M40360</guid>
      <dc:creator>skalliger</dc:creator>
      <dc:date>2017-01-31T12:53:58Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204503#M40361</link>
      <description>&lt;P&gt;We are also experiencing this on our universal forwarders.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jun 2017 18:16:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204503#M40361</guid>
      <dc:creator>Kieffer87</dc:creator>
      <dc:date>2017-06-02T18:16:41Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204504#M40362</link>
      <description>&lt;P&gt;do you get this error on both windows and linux forwarders or windows only?&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jun 2017 18:46:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204504#M40362</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2017-06-02T18:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204505#M40363</link>
      <description>&lt;P&gt;I get it on both but far more windows than linux. Also not all forwarders are experiencing this error despite running the same 6.5.3 version of Splunk.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jun 2017 20:05:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204505#M40363</guid>
      <dc:creator>Kieffer87</dc:creator>
      <dc:date>2017-06-02T20:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204506#M40364</link>
      <description>&lt;P&gt;Since I created this thread I've seen this error on different UF versions (6.3.x, 6.4.x and our most recent UF version 6.5.3) as well as on different OS (windows, linux, macOS).&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 08:37:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204506#M40364</guid>
      <dc:creator>pilzi81</dc:creator>
      <dc:date>2017-06-06T08:37:07Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204507#M40365</link>
      <description>&lt;P&gt;Although we see events from the forwarder but we see this error. Any idea what this error means?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2017 15:58:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204507#M40365</guid>
      <dc:creator>ss026381</dc:creator>
      <dc:date>2017-06-12T15:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204508#M40366</link>
      <description>&lt;P&gt;This is a known Universal Forwarder issue (SPL-103209) effecting 6.3 and above.  Currently there is no patch but the error is benign and can be ignored.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2017 11:10:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204508#M40366</guid>
      <dc:creator>jnew_splunk</dc:creator>
      <dc:date>2017-06-14T11:10:09Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204509#M40367</link>
      <description>&lt;P&gt;Hello i have this issue on each restart of UF 7.0.8, is there some updates?&lt;BR /&gt;
Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 01 Feb 2019 13:46:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/204509#M40367</guid>
      <dc:creator>LCanac31</dc:creator>
      <dc:date>2019-02-01T13:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: Why are universal forwarders reporting error "Metric with the name thruput:thruput already registered"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/680974#M113767</link>
      <description>&lt;P&gt;When I installed and started Universal Forwarder 9.1.0.1, the following ERROR occurred:&lt;/P&gt;&lt;P&gt;ERROR Metrics - Metric with name='thruput:thruput' already registered&lt;BR /&gt;ERROR Metrics - Metric with name='thruput:idxSummary' already registered&lt;/P&gt;&lt;P&gt;Is this issue still persisting even with version 9.1.0.1?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2024 07:35:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-universal-forwarders-reporting-error-quot-Metric-with/m-p/680974#M113767</guid>
      <dc:creator>tskht</dc:creator>
      <dc:date>2024-03-18T07:35:10Z</dc:date>
    </item>
  </channel>
</rss>

