Hello! We have a database that can be consulted by 4 different connection nodes. 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. 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? Greetings and thanks! ... View more