Skip to main content
Sumo Logic

Local Configuration File Management for New Collectors and Sources

With local configuration file management, you cannot use the API or the web app for source configuration. In the web app, the Add Source option is disabled on the Manage Data > Collection > Collection page (Manage > Collection in the classic UI).

Step 1. Determine the sources you need

Depending on the data you’re planning to upload to Sumo Logic, there are several sources you can configure. For details, see Sources.

Step 2. Build the source JSON configuration file(s)

The JSON configuration file allows you to define Sources for collection. For JSON configuration details, see Use JSON to Configure Sources

If you have an existing collector with sources of the same types that you are about to configure, you can obtain their JSON configuration from the Sumo web app, as described in Step 1 of Local Configuration File Management for Existing Collectors and Sources, and use that JSON  as a starting point for creating source configurations.

There are two ways to implement local configuration file management:

  • Specify all sources in a single JSON file. For more information, see "Define one source in a JSON file" on Local Configuration File Management.
  • Use multiple JSON files to specify your sources, and put all of those files in a single folder. You can put each source definition in own file, or define multiple sources per file, if you like. For more information see "Define Multiple Sources in a JSON File" on Local Configuration File Management.

Step 3. Install collector with syncSources parameter

When installing the collector, specify the syncSources parameter. See the topics in Installed Collectors for information on specifying parameters during installation.

Parameter Type Description
syncSources String Sets the JSON file describing sources to configure on registration, which will be continuously monitored and synchronized with the Collector's configuration.

For example, for command-line installation, supplying the Access ID and Access Key, syncSources, and the collector name:

sudo ./SumoCollector.sh -q -Vsumo.accessid=<accessId> -Vsumo.accesskey=<accessKey> -VsyncSources=<filepath> -Vcollector.name=<name>

For legacy collectors (versions prior to 19.137), add the syncSources parameter to the sumo.conf  file before starting the collector for the first time.

Making changes to the configuration files

After a collector is registered with the syncSources parameter, you can edit the source JSON file(s) at any time to modify source attributes and add new sources. To remove an existing source, delete the associated JSON object; if the source you want to remove is the only source defined in a JSON file, delete the file.  

After you finalize changes to a JSON configuration file(s), test the changes with a collector on a host that is NOT in production. After the file is validated, deploy it to each host with sources whose JSON configuration you want to update. Collectors continually watch the JSON configuration files for changes and immediately process any changes.