<?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 Hidden syslog configuration on heavy forwarders in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/675425#M113036</link>
    <description>&lt;P&gt;My organization has a handful of heavy forwarders that were configured to listen to syslog sources through udp://514. This was set up by a 3rd party, and now we are trying to understand the configuration. Searching the heavy forwarders' /etc/* recursively for "514", "tcp", "udp", "syslog", or "SC4S" returns no relevant results.&lt;/P&gt;&lt;P&gt;We know syslog is working, because we have multiple sources that are pointed at the heavy forwarders using udp over port 514 and their data is being indexed.&lt;/P&gt;&lt;P&gt;Curiously, when a new syslog source is pointed at the HFs, a new index with a random name pops up in our LastChanceIndex. We have no idea how any of this is configured - the index selection, or the syslog listener. We usually create an index that matches the name given, since we've never been able to find the config to set it manually.&lt;/P&gt;&lt;P&gt;Any suggestions on how syslog might be set up, or what else I could try searching for?&lt;/P&gt;</description>
    <pubDate>Thu, 25 Jan 2024 17:33:14 GMT</pubDate>
    <dc:creator>Dominic32</dc:creator>
    <dc:date>2024-01-25T17:33:14Z</dc:date>
    <item>
      <title>Hidden syslog configuration on heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/675425#M113036</link>
      <description>&lt;P&gt;My organization has a handful of heavy forwarders that were configured to listen to syslog sources through udp://514. This was set up by a 3rd party, and now we are trying to understand the configuration. Searching the heavy forwarders' /etc/* recursively for "514", "tcp", "udp", "syslog", or "SC4S" returns no relevant results.&lt;/P&gt;&lt;P&gt;We know syslog is working, because we have multiple sources that are pointed at the heavy forwarders using udp over port 514 and their data is being indexed.&lt;/P&gt;&lt;P&gt;Curiously, when a new syslog source is pointed at the HFs, a new index with a random name pops up in our LastChanceIndex. We have no idea how any of this is configured - the index selection, or the syslog listener. We usually create an index that matches the name given, since we've never been able to find the config to set it manually.&lt;/P&gt;&lt;P&gt;Any suggestions on how syslog might be set up, or what else I could try searching for?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2024 17:33:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/675425#M113036</guid>
      <dc:creator>Dominic32</dc:creator>
      <dc:date>2024-01-25T17:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: Hidden syslog configuration on heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/675431#M113037</link>
      <description>&lt;P&gt;Hi! you'll want to poke thru the docs on splunk config files:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.1.2/Admin/AboutConfigurationFiles" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/9.1.2/Admin/AboutConfigurationFiles&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;But tldr is I would use "btool" -&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.1.2/Troubleshooting/Usebtooltotroubleshootconfigurations" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/9.1.2/Troubleshooting/Usebtooltotroubleshootconfigurations&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and you'll want to go hunting for "inputs.conf" - this is where your spunk instances would be taking the data in, then comb thru props.conf - where the sourcetypes and event parsing/transformation/routing happens..&lt;BR /&gt;&lt;BR /&gt;It is also common to have splunk co-located with a syslog listener who puts logs down that we pick up. So a quick `ss -tulpn` or `netstat -tulpn` will show what ports, if any, are open on your Heavy Forwarders.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;so getting good with btool or reviewing Inputs and sourcetypes in your splunk ui will be key&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2024 17:58:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/675431#M113037</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2024-01-25T17:58:25Z</dc:date>
    </item>
    <item>
      <title>Re: Hidden syslog configuration on heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/675443#M113039</link>
      <description>&lt;P&gt;As stated I've tried searching through all files within /etc/* (including all .conf files) for the following:&amp;nbsp;&lt;SPAN&gt;"514", "tcp", "udp", "syslog", or "SC4S". I get no results. You mentioned I should check inputs.conf, but I've already done this and found nothing - could you elaborate on what exactly I should be searching for? Are there additional keywords I should try?&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;I confirmed that the Heavy Forwarders are listening on port 514. Syslog is working... I just don't see how it's configured.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Edit: I also want to ask - what could btool find that a sudo grep search wouldn't have located?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2024 20:45:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/675443#M113039</guid>
      <dc:creator>Dominic32</dc:creator>
      <dc:date>2024-01-25T20:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: Hidden syslog configuration on heavy forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/677308#M113248</link>
      <description>&lt;P&gt;SC4S was running in a docker container through Podman. Mystery solved!&lt;/P&gt;&lt;P&gt;&lt;A href="https://splunk.github.io/splunk-connect-for-syslog/main/gettingstarted/getting-started-splunk-setup/" target="_blank"&gt;Splunk Setup - Splunk Connect for Syslog&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Feb 2024 17:00:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Hidden-syslog-configuration-on-heavy-forwarders/m-p/677308#M113248</guid>
      <dc:creator>Dominic32</dc:creator>
      <dc:date>2024-02-12T17:00:37Z</dc:date>
    </item>
  </channel>
</rss>

