Data Monitoring / Splunk Ingestion & Search Evidence
Splunk: Missing host coverage
A total event count looks normal although a critical host is absent. Compare distinct reporting hosts with an inventory of expected active hosts.
Environment and inputs: Splunk Enterprise / Splunk Cloud Platform; SPL and event-processing behavior must be checked against the deployed release and collection topology.
Failure scenario
A total event count looks normal although a critical host is absent. Confirm the cause before choosing a fix.
Evidence to collect
Compare distinct reporting hosts with an inventory of expected active hosts. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Maintain an expected-source coverage check and account explicitly for decommissioning or maintenance. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for missing host coverage using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.