<?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: Universal forwarders ingestion behind F5 LB in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535377#M89792</link>
    <description>Accepting is good to mark a problem as solved so someone can find solutions in the future.&lt;BR /&gt;Upvote means clicking the Karma button.</description>
    <pubDate>Mon, 11 Jan 2021 17:32:29 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2021-01-11T17:32:29Z</dc:date>
    <item>
      <title>Universal forwarders ingestion behind F5 LB</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535257#M89770</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I should find a solution to ingest a file on a network share that is managed from two server behind a load balancer. In my case i should install an UF on every server and check the same file, if i have well understood the UF has not a kind of cluster/balancing awareness so if the file is updated from one server i risk to have the same data ingested from both of them.&lt;BR /&gt;How i can manage this kind of behaviour and avoid that new data is ingested from the temporary passive server ?&lt;/P&gt;&lt;P&gt;Unfortunately i cannot use a third server to monitor the file and bypass the issue.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 09 Jan 2021 11:25:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535257#M89770</guid>
      <dc:creator>giuces</dc:creator>
      <dc:date>2021-01-09T11:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarders ingestion behind F5 LB</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535262#M89772</link>
      <description>&lt;P&gt;If the file is available from both servers then only 1 UF needs to monitor it.&amp;nbsp; The other UF must not monitor the same file or duplicate data is likely.&lt;/P&gt;</description>
      <pubDate>Sat, 09 Jan 2021 13:34:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535262#M89772</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-01-09T13:34:10Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarders ingestion behind F5 LB</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535330#M89782</link>
      <description>&lt;P&gt;I Rich,&lt;/P&gt;&lt;P&gt;thank you for the reply. It is a valid solution, but in case i have to use UF in both nodes is there a possible workaround ?&lt;/P&gt;&lt;P&gt;thanks and regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jan 2021 10:48:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535330#M89782</guid>
      <dc:creator>giuces</dc:creator>
      <dc:date>2021-01-11T10:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarders ingestion behind F5 LB</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535342#M89786</link>
      <description>&lt;P&gt;There is no workaround, which is why Splunk explicitly advises against monitoring the same directory/file by more than one forwarder.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jan 2021 13:38:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535342#M89786</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-01-11T13:38:22Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarders ingestion behind F5 LB</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535358#M89789</link>
      <description>&lt;P&gt;thank you, i accepted the solution. I hope it is the right way to upvote it.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jan 2021 15:26:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535358#M89789</guid>
      <dc:creator>giuces</dc:creator>
      <dc:date>2021-01-11T15:26:00Z</dc:date>
    </item>
    <item>
      <title>Re: Universal forwarders ingestion behind F5 LB</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535377#M89792</link>
      <description>Accepting is good to mark a problem as solved so someone can find solutions in the future.&lt;BR /&gt;Upvote means clicking the Karma button.</description>
      <pubDate>Mon, 11 Jan 2021 17:32:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-forwarders-ingestion-behind-F5-LB/m-p/535377#M89792</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-01-11T17:32:29Z</dc:date>
    </item>
  </channel>
</rss>

