Hey, thank you for your help, here is what you requested:
prospectors:
# Each - is a prospector. Below are the prospector specific configurations
-
# Paths that should be crawled and fetched. Glob based paths.
# To fetch all ".log" files from a specific level of subdirectories
# /var/log/*/*.log can be used.
# For each file found under this path, a harvester is started.
# Make sure not file is defined twice as this can lead to unexpected behaviour.
paths:
- "/coriant/sdn/logs/tc/Heap_Logs/*"
#- c:\programdata\elasticsearch\logs\*
input_type: log
fields:
log_type: heap
-
paths:
- "/coriant/sdn/logs/tc/GC_Logs/*"
input_type: log
fields:
log_type: GC
-
2 prospectors to different files (One to Heap_Logs, another to GC_Logs)
-
im using filebeat 1.3
-
here is the logging from filebeat, i havent seen it before, but still i dont understand what it meants, the file path is working fine for the first prospector but not for the second even though they are very similar
2016-10-28T10:12:06+01:00 CRIT Config error: Error reading config file: YAML config parsing failed on /etc/filebeat/filebeat.yml: yaml: unmarshal errors: line 148: cannot unmarshal !!str `/corian...` into config.ProspectorConfig. Exiting.