<?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 Splunk is ingesting archive files of syslog data that has already been ingested. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325628#M60522</link>
    <description>&lt;P&gt;our setup 2 SH, 1 deployment server, 1 license server and 2 indexers , our two indexers are also syslog servers and they read the input file directly from syslog folder for indexing i suspect Splunk is ingesting archive files of syslog data that has already been ingested How do i verify this ?&lt;/P&gt;</description>
    <pubDate>Thu, 07 Sep 2017 10:31:36 GMT</pubDate>
    <dc:creator>hrithiktej</dc:creator>
    <dc:date>2017-09-07T10:31:36Z</dc:date>
    <item>
      <title>Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325628#M60522</link>
      <description>&lt;P&gt;our setup 2 SH, 1 deployment server, 1 license server and 2 indexers , our two indexers are also syslog servers and they read the input file directly from syslog folder for indexing i suspect Splunk is ingesting archive files of syslog data that has already been ingested How do i verify this ?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 10:31:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325628#M60522</guid>
      <dc:creator>hrithiktej</dc:creator>
      <dc:date>2017-09-07T10:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325629#M60523</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;
you can run a search like this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=your_index
| stats count by source
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and verify if the eventcount for each source is the same of the file or not.&lt;/P&gt;

&lt;P&gt;otherwise you can run&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=your_index
| stats count by _raw
| where count&amp;gt;1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;if there are results, you have duplicated events.&lt;/P&gt;

&lt;P&gt;You can also verify if your monitored servers are configured to send to both the hosts or not.&lt;BR /&gt;
The best way is to have a Load Balancer between monitored servers and Indexers to be sure of syslog flow ingestion.&lt;/P&gt;

&lt;P&gt;Splunk can run a syslog server, and it's efficient (if you have quick disks), why do you use a syslog server on your indexers?&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 10:43:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325629#M60523</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-09-07T10:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325630#M60524</link>
      <description>&lt;P&gt;Thanks&lt;BR /&gt;
I ran index=* | stats count by _raw | where count&amp;gt;1 for last 24hrs and I see more than 4 hundred thousand events. &lt;/P&gt;

&lt;P&gt;We do have a f5 load balancer before the indexer/syslog cluster and I do not know why our previous splunk admin set the indexers and syslog servers on same box. &lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 10:56:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325630#M60524</guid>
      <dc:creator>hrithiktej</dc:creator>
      <dc:date>2017-09-07T10:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325631#M60525</link>
      <description>&lt;P&gt;It could not be a problem to have both Indexers and syslog servers on the same machines,it depends only by the load that they have to manage, if you have few events to ingest and index you can leave them on Indexers, if instead you have many events it's surely better to have two dedicated Heavy Forwarders for syslog ingestion.&lt;BR /&gt;
Anyway per the log duplication, you have to check your F5 configuration and what is the destination host of your monitored servers, maybe they are configurated to directly send to both the Indexers addresses instead Virtual IP.&lt;BR /&gt;
Bye.&lt;BR /&gt;
Giuseppe&lt;BR /&gt;
N.B.: if your satisfied by this answer, please accept or upvote it&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 11:09:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325631#M60525</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-09-07T11:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325632#M60526</link>
      <description>&lt;P&gt;From the query and the results that i told you earlier do you mean to say we have duplication of data issue? and I checked the f5 config we have both our indexers mapped to a virtual IP and all the monitored hosts like FWs and switches have this VIP entry in their logging for syslog setup.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 12:40:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325632#M60526</guid>
      <dc:creator>hrithiktej</dc:creator>
      <dc:date>2017-09-07T12:40:21Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325633#M60527</link>
      <description>&lt;P&gt;Only one additional check, run:&lt;BR /&gt;
 index=* | stats count by host _raw&lt;BR /&gt;
to verify if the doubled log is sent by one or two hosts (it's really difficoult that the same log is sent by different hosts!).&lt;/P&gt;

&lt;P&gt;About the reason of this, the only possibility is that there are two sources for the same data, two sources because F5 sends to both the indexers or because there are two inputs.confs.&lt;/P&gt;

&lt;P&gt;Verify F5 configuration.&lt;BR /&gt;
Then check your inputs configurations to understand if there are more inputs for the same source.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 12:56:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325633#M60527</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-09-07T12:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325634#M60528</link>
      <description>&lt;P&gt;Thanks! when i run index=* | stats count by host _raw i do see multiple logs for same ip however the count is 1&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 13:18:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325634#M60528</guid>
      <dc:creator>hrithiktej</dc:creator>
      <dc:date>2017-09-07T13:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325635#M60529</link>
      <description>&lt;P&gt;Are your hostnames expressed as IPs?&lt;BR /&gt;
If you didn't configured hostname run the same search using IP instead host.&lt;BR /&gt;
The scope of this search is exclude same logs that arrive from different hosts.&lt;BR /&gt;
bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Sun, 10 Sep 2017 05:56:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325635#M60529</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-09-10T05:56:14Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk is ingesting archive files of syslog data that has already been ingested.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325636#M60530</link>
      <description>&lt;P&gt;Thanks Even when I run index=* | stats count by IP _raw I do see multiple logs for the same IP. Is this Duplication?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2017 09:37:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-is-ingesting-archive-files-of-syslog-data-that-has/m-p/325636#M60530</guid>
      <dc:creator>hrithiktej</dc:creator>
      <dc:date>2017-09-11T09:37:11Z</dc:date>
    </item>
  </channel>
</rss>

