Hello All, This is a known bug in Splunk and we are working to address. Please use the following work around in the interim. Create a health.conf entry in /opt/splunk/etc/system/local on the affected machines being sure to restart splunk after the entry is made. adding: [health_reporter] aggregate_ingestion_latency_health = 0 [feature:ingestion_latency] alert.disabled = 1 disabled = 1 Let me know if you have any questions or concerns
... View more