Question 260
A manufacturing site streams machine logs from universal forwarders. Observed: Indexer input sockets show no connections because the configured receiver port differs from the forwarder destination. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (A connectivity test and _internal logs show established S2S sessions on the correct port) to the original warning (Indexer input sockets show no connections because the configured receiver port differs from the forwarder destination). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
This is an unrelated recovery test. It is connected to: Repeated full exports produce duplicates because the source lacks a reliable change cursor. The present source situation requires: A connectivity test and _internal logs show established S2S sessions on the correct port.
The proposed check applies to: Full parsing and routing can consume substantial resources on heavy forwarders. The current failure was: Indexer input sockets show no connections because the configured receiver port differs from the forwarder destination. Its validation must test: A connectivity test and _internal logs show established S2S sessions on the correct port.
That gate watches a different case: Each line of a Java stack trace appears as an independent event after ingestion. It does not detect the current warning: Indexer input sockets show no connections because the configured receiver port differs from the forwarder destination. The necessary confirmation is: A connectivity test and _internal logs show established S2S sessions on the correct port.