<?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 Forwarder - Monitor same log source twice in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592717#M103745</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/239315"&gt;@joshuasolman&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;did you already tested the steps&amp;nbsp; described at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.5/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.5/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system&lt;/A&gt;&amp;nbsp;?&lt;/P&gt;&lt;P&gt;In this page is descripted the configuration to send all data to indexers and a part of them (identified by a regex) to a third party system.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Wed, 06 Apr 2022 15:26:07 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2022-04-06T15:26:07Z</dc:date>
    <item>
      <title>Is it possible to deploy a universal forwarder that monitors the same log source twice and routes the data differently?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592711#M103743</link>
      <description>&lt;P&gt;Hello would it be possible to deploy a universal forwarder that monitors the same log source twice and routes the data differently based on what i want to collect?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example, two different apps on the UF&amp;nbsp;&lt;/P&gt;
&lt;P&gt;App1:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Inputs.conf - All winevent logs (including security)&lt;/P&gt;
&lt;P&gt;Outputs.conf - Going to indexer&lt;/P&gt;
&lt;P&gt;App2:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Inputs.conf - WinEventSecurity logs (whitelisted for two events)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Outputs.conf - Seperate destination&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would there be any issues reading the security log twice or would there be confliction?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 15:35:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592711#M103743</guid>
      <dc:creator>joshuasolman</dc:creator>
      <dc:date>2022-04-06T15:35:48Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder - Monitor same log source twice</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592717#M103745</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/239315"&gt;@joshuasolman&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;did you already tested the steps&amp;nbsp; described at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.5/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.5/Forwarding/Routeandfilterdatad#Replicate_a_subset_of_data_to_a_third-party_system&lt;/A&gt;&amp;nbsp;?&lt;/P&gt;&lt;P&gt;In this page is descripted the configuration to send all data to indexers and a part of them (identified by a regex) to a third party system.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 15:26:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592717#M103745</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-04-06T15:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder - Monitor same log source twice</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592719#M103746</link>
      <description>&lt;P&gt;I did see this, but i see it only mentions Heavy Forwarders. Is it possible to do this on Universal Forwarders?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 15:29:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592719#M103746</guid>
      <dc:creator>joshuasolman</dc:creator>
      <dc:date>2022-04-06T15:29:06Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder - Monitor same log source twice</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592722#M103747</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/239315"&gt;@joshuasolman&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;no, only on HFs or Indexers, because the Parsing Phase isn't present on UFs.&lt;/P&gt;&lt;P&gt;Maybe you could send all data both to Splunk and Third Party system and then filter on those systems, in this case you can configure UFs to send to both the destinations.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 15:38:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592722#M103747</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-04-06T15:38:59Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder - Monitor same log source twice</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592747#M103751</link>
      <description>&lt;P&gt;I think you will need to create a routing rule and add both destinations in outputs.conf&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 18:22:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592747#M103751</guid>
      <dc:creator>SinghK</dc:creator>
      <dc:date>2022-04-06T18:22:59Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to deploy a universal forwarder that monitors the same log source twice and routes the data different</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592748#M103752</link>
      <description>&lt;P&gt;No, you can't. As &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt; already pointed out, UF is a relatively simple tool thst doesn't allow for many advanced index-time operations that indexers and HFs allow. Furthermore, you cannot (short of doing some dirty tricks with symlinking in case of file monitoring inputs) define the same stanza twice. So you can't have two separate winevent://security sources. You'd just overwrite some settings from the first definition with the second one.&lt;/P&gt;&lt;P&gt;You could (although it's not supported and not heavily tested I suppose) try to install and run two separate instances of UF on one host. But it kinda defeats the purpose - if you're gonna use it to send your events to another solution, why not use that solution's dedicated monotoring tool?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 18:29:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-deploy-a-universal-forwarder-that-monitors-the/m-p/592748#M103752</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-04-06T18:29:46Z</dc:date>
    </item>
  </channel>
</rss>

