The configs are concatenated in alphabetical order, so no config takes priority over another, which is why it is important to use conditionals to ...
The path to the Logstash config for the main pipeline. If you specify a directory or wildcard, config files are read from the directory in alphabetical order.
... reason, the order of the files does matter: input-filter-output: ~/util/logstash-1.5.4 /bin/logstash -f ./conf.d/input-50-email-sending.conf…
The plugin loops between discovering new files and processing each
I then have another config file for the firewall filter 02-firewall.conf filter { if [type] == "firewall" { } }. So my question is how or in what order does ...
Mutations in a config file are executed in this order: coerce; rename; update; replace; convert; gsub; uppercase; capitalize; lowercase; strip ...
Order only matters within blocks. For this very contrived example, let's say that my files get ordered in such a way that the config file has a filter then an output then ...
they are applied in the order of their appearance in the configuration file.
Actually there is no support for "include" and Logstash is not able to load a pipeline splitted in different files in order to reuse common parts.
Load the Logstash config from a specific file or directory. If a directory is given, all files in that directory will be concatenated in lexicographical order and then ...