https://community.splunk.com/t5/Getting-Data-In/Possible-data-duplication-with-db-connect/m-p/641483#M109399 <P>Hello!<BR />We have a database that can be consulted by 4 different connection nodes.</P><P>To generate high availability in the event ingestion of this database, I intend to create in the db-connect app 4 entries, one pointing to each connection node.</P><P>My query is if, when performing the Splunk ingestion, each input task will be able to understand that the events of the database table have already been indexed by another input and ignore it so as not to duplicate the information?</P><P>Greetings and thanks!</P> Wed, 26 Apr 2023 17:27:54 GMT csib 2023-04-26T17:27:54Z https://community.splunk.com/t5/Getting-Data-In/Possible-data-duplication-with-db-connect/m-p/641483#M109399 <P>Hello!<BR />We have a database that can be consulted by 4 different connection nodes.</P><P>To generate high availability in the event ingestion of this database, I intend to create in the db-connect app 4 entries, one pointing to each connection node.</P><P>My query is if, when performing the Splunk ingestion, each input task will be able to understand that the events of the database table have already been indexed by another input and ignore it so as not to duplicate the information?</P><P>Greetings and thanks!</P> Wed, 26 Apr 2023 17:27:54 GMT https://community.splunk.com/t5/Getting-Data-In/Possible-data-duplication-with-db-connect/m-p/641483#M109399 csib 2023-04-26T17:27:54Z https://community.splunk.com/t5/Getting-Data-In/Possible-data-duplication-with-db-connect/m-p/641504#M109400 <P>Nope.&nbsp; Inputs are ignorant of each other so they will happily pull in the same events.&nbsp; Also, Splunk does not de-duplicate data on input.</P> Wed, 26 Apr 2023 20:57:06 GMT https://community.splunk.com/t5/Getting-Data-In/Possible-data-duplication-with-db-connect/m-p/641504#M109400 richgalloway 2023-04-26T20:57:06Z