<?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: SC4S parser in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/SC4S-parser/m-p/750808#M119270</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/170906"&gt;@livehybrid&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for this. I looked at the parsing documentation earlier. Is there not a simpler way to do this as I don't need to rewrite fields etc as I have a TA doing it. All I need is if syslog from this HOST/IP then send to index=opnsense, is this achievable with one parser config or is what you already stated the only way of doing it?&lt;/P&gt;</description>
    <pubDate>Thu, 31 Jul 2025 13:03:08 GMT</pubDate>
    <dc:creator>L_Petch</dc:creator>
    <dc:date>2025-07-31T13:03:08Z</dc:date>
    <item>
      <title>SC4S parser</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/SC4S-parser/m-p/750799#M119268</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to send all syslog data from opnsense to a specific index. As this is not a known vender source what is the easiest way to do this? I have seen that you can create a parser based on certain factors so guessing this would be the easiest way? If so does anyone have a good parser guide?&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jul 2025 10:04:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/SC4S-parser/m-p/750799#M119268</guid>
      <dc:creator>L_Petch</dc:creator>
      <dc:date>2025-07-31T10:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: SC4S parser</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/SC4S-parser/m-p/750804#M119269</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/260662"&gt;@L_Petch&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you havent already, check out&amp;nbsp;&lt;A href="https://splunk.github.io/splunk-connect-for-syslog/2.44.2/gettingstarted/create-parser/" target="_blank"&gt;https://splunk.github.io/splunk-connect-for-syslog/2.44.2/gettingstarted/create-parser/&lt;/A&gt;&amp;nbsp;which has a guide on how to create custom parsers. This is probably the best way because it prevents finding a potentially fragile alternative process for identifying and routing the data (e.g. when it lands in Splunk with Props/Transforms).&lt;/P&gt;&lt;P&gt;Here is a sample to get you started:&lt;BR /&gt;In&amp;nbsp;&lt;SPAN&gt;/opt/sc4s/local/config/app_parsers/&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;# app-opnsense.conf
application app-opnsense[sc4s-network-source] {
    filter {
        program("filterlog" flags(prefix))
        or program("opnsense" flags(prefix))
        or host("opnsense*" type(glob))
        or message("opnsense" flags(substring))
    };
    parser {
        p_set_netsource_fields(
            vendor("pfsense")  # Use pfsense as base
            product("opnsense")
        );
    };
};&lt;/LI-CODE&gt;&lt;P&gt;Then create the destination in&amp;nbsp;/opt/sc4s/local/config/destinations/:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;# dest-opnsense.conf
destination d_opnsense {
    splunk(
        class(splunk_hec)
        template("$(format-splunk-hec)")
        hec_token("YOUR_HEC_TOKEN")
        url("https://your-splunk:8088/services/collector/event")
        index("opnsense")
        source("${.splunk.source}")
        sourcetype("opnsense:syslog")
    );
};

log {
    source(s_network);
    filter(f_is_source_identified);
    if (match("opnsense" value("fields.sc4s_vendor"))) {
        destination(d_opnsense);
        flags(flow-control,final);
    };
};&lt;/LI-CODE&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jul 2025 12:21:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/SC4S-parser/m-p/750804#M119269</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-07-31T12:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: SC4S parser</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/SC4S-parser/m-p/750808#M119270</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/170906"&gt;@livehybrid&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for this. I looked at the parsing documentation earlier. Is there not a simpler way to do this as I don't need to rewrite fields etc as I have a TA doing it. All I need is if syslog from this HOST/IP then send to index=opnsense, is this achievable with one parser config or is what you already stated the only way of doing it?&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jul 2025 13:03:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/SC4S-parser/m-p/750808#M119270</guid>
      <dc:creator>L_Petch</dc:creator>
      <dc:date>2025-07-31T13:03:08Z</dc:date>
    </item>
  </channel>
</rss>

