Symantec Endpoint Detection and Response (EDR) stopped sending events to Splunk log host.
Sometimes the forwarding of events to Splunk freezes and EDR stops sending logs.
The SEDR token appears to expire frequently. Even though the token expiration problem may eventually appear to resolve itself the Splunk connector will still try to run the same query and never forward any recent events that have occurred.
As a workaround disable the Splunk integration and re-enable it. After this EDR will send events again.
Method 1 - Update the time range filter to a more recent timestamp
The output of the CLI command df -h may show a high amount of disk usage for the partition that stores events.
For example, the output of df -h might show the elasticsearch partition at 85% of capacity. When the elasticsearch partition reaches 80%, the emergency purge checks and purges data every 15 minutes until the disk capacity reaches 75%. In this scenario, EDR may be purging events so quickly that the data set EDR is trying to forward no longer exists.
It is possible that the issue being seen is not related to the issues and solutions presented in this case. If the logs instead show that the upload of data failed or that the server was busy when EDR is attempting to upload events to Splunk then we recommend referring to article 175221, https://knowledge.broadcom.com/external/article/175221