<?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 Tagging Heavy Forwarders in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Tagging-Heavy-Forwarders/m-p/603734#M13061</link>
    <description>&lt;P&gt;This is a &lt;STRONG&gt;tip&lt;/STRONG&gt;, not a &lt;STRONG&gt;question&lt;/STRONG&gt;.&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face_with_big_eyes:"&gt;😃&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When you have a large solution, you can see on the log data: what the UF name that data comes from, what Index server data are stored on.&amp;nbsp; What you do not see are what Heavy Forwarders data are passing trough.&amp;nbsp; Here is an app that do just that.&amp;nbsp; Adding an extra field does not use extra license, since only _raw length are calculated.&lt;/P&gt;&lt;P&gt;Make an app that you sends to all HF servere:&lt;/P&gt;&lt;P&gt;app name: set_name_gateway_hf&lt;/P&gt;&lt;P&gt;props.conf (will apply to all data)&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;[source::...]
TRANSFORMS_set_hf_server_name = set_hf_server_name&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;transforms.conf&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;[set_hf_server_name]
INGEST_EVAL = splunk_hf_name := splunk_server&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This will use the Splunk HF server name from &lt;STRONG&gt;etc/system/local/server.conf&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jun 2022 10:16:17 GMT</pubDate>
    <dc:creator>jotne</dc:creator>
    <dc:date>2022-06-29T10:16:17Z</dc:date>
    <item>
      <title>Tagging Heavy Forwarders</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Tagging-Heavy-Forwarders/m-p/603734#M13061</link>
      <description>&lt;P&gt;This is a &lt;STRONG&gt;tip&lt;/STRONG&gt;, not a &lt;STRONG&gt;question&lt;/STRONG&gt;.&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face_with_big_eyes:"&gt;😃&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When you have a large solution, you can see on the log data: what the UF name that data comes from, what Index server data are stored on.&amp;nbsp; What you do not see are what Heavy Forwarders data are passing trough.&amp;nbsp; Here is an app that do just that.&amp;nbsp; Adding an extra field does not use extra license, since only _raw length are calculated.&lt;/P&gt;&lt;P&gt;Make an app that you sends to all HF servere:&lt;/P&gt;&lt;P&gt;app name: set_name_gateway_hf&lt;/P&gt;&lt;P&gt;props.conf (will apply to all data)&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;[source::...]
TRANSFORMS_set_hf_server_name = set_hf_server_name&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;transforms.conf&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;[set_hf_server_name]
INGEST_EVAL = splunk_hf_name := splunk_server&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This will use the Splunk HF server name from &lt;STRONG&gt;etc/system/local/server.conf&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jun 2022 10:16:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Tagging-Heavy-Forwarders/m-p/603734#M13061</guid>
      <dc:creator>jotne</dc:creator>
      <dc:date>2022-06-29T10:16:17Z</dc:date>
    </item>
  </channel>
</rss>

