Page Comparison

...

In general terms, the filefetcher extension works by processing one or more paths defined in its configuration and uploading the contents of the files in those paths line by line. Such configuration is defined in the Ansible role ‘deam-packs’ along with the rest of settings for the EA Manager. The following instructions specify the process to add a new configuration to the Files Fetcher extension:

1. Edit the inventory file we used in our Devo EA Manager deployment.

2. Under the “vars“ section, add one of the following fields (matching our endpoint Operating System).

• Windows

  Code Block
  deam_fleet_config_devoext_fetchfiles_paths_win:

• Linux

  Code Block
  deam_fleet_config_devoext_fetchfiles_paths_nix:

• Darwin

  Code Block
  deam_fleet_config_devoext_fetchfiles_paths_darwin:

...

If you need to re-configure a pattern to a different tag:

1. Remove the pattern that we want to reconfigure in the inventory file and deploy the deam-packs playbook (ansible-playbook -i inventories/your_inventory.yaml playbooks/deam-packs.yaml). As en example in the below screenshot, we removed the highlighted pattern line.
   

...

1. Image Added

2. Wait until the configuration is propagated to the agents. The default value for configuration refresh is 15 minutes and is set in the config_refresh tag in the inventory.

3. Enable the virtual environment by running:

   Code Block
   source "/opt/ansible-2.9/venv/bin/activate"

4. Once the configuration is propagated, create the pattern again, pointing to the new tag in the inventory file and deploy the deam-packs playbook (ansible-playbook -i inventories/your_inventory.yaml playbooks/deam-packs.yaml) . As an example in the below screenshot, we have added the pattern again, but pointing to a new tag.
   

...

1. Image Added

2. The data will start ingesting from the beginning of the file in the new tag.

Performance considerations

...