Symptoms: 

When using Local File Management mode and updating the source.json file to remove a Source from a Collector the Source is not getting removed and continues to ingest data.

Possible Cause:

The JSON supplied to the Collector cannot be validated by the Collector and as a result, is not applied. This could be due to multiple filters supplied with the same "Name" key within a Source. 

The Collectors log files should contain more information on any JSON validation issues that might be occurring. Within the collector.log file, you will see messages with the following content.

com.sumologic.scala.collector.auth.CollectorRegistrationManager - [main] Response code is 200 with warnings:

Within this message, there should be more information on any validation issues encountered. 

Full Example:

2017-06-09 13:46:10,474 +0200 [JsonSync Manager] INFO com.sumologic.scala.collector.auth.CollectorRegistrationManager - [main] Response code is 200 with warnings: List(Key: validation.fields.invalid, Message: All filters must have different names.), errors: List()

Resolution Steps:

If you correct validation issues (such as removing duplicate filter name “TEST123” from the affected sources), you should be able to save the file after deleting the sources, and see the changes taking effect in Sumo UI (no collector restart required). 

After performing these steps, and if this is resolved, in collector.log you should see the following message with an empty list of warnings and errors:

2017-06-15 11:34:11,513 -0700 [JsonSync Manager] INFO com.sumologic.scala.collector.auth.CollectorRegistrationManager - [main] Response code is 200 with warnings: List(), errors: List()

2017-06-15 11:34:11,513 -0700 [JsonSync Manager] INFO com.sumologic.scala.collector.JsonFileSyncManager - Sources successfully synchronized