Suggestion: placeholders in logstash.conf
Description
Gliffy Diagrams
Activity
Show:
Philippe Weber January 24, 2015 at 8:20 PM
Following similar discussion in https://github.com/elasticsearch/logstash/issues/1629
templating of the file should be left to dedicated upfront solution (puppet, m4...)
Jason Kendall April 17, 2014 at 6:54 PM
Confirming the feature request.
However, as a workaround, prior to launching, you could use 'sed' to manipulate the config file based on your requirements.
It would be nice if one could use placeholders in logstash.conf that are filled, for instance, from system properties.
Background: We are deploying logstash on a number of machines - development environments, testing environments and production. It would be nice and more failsafe if we could use the same logstash.conf file in all environments. But there are obviously some differences: the paths of the log files in the file plugin, some tags / special fields to label the environment, the host, cluster and port of the elasticsearch output. One way to enable this would be to allow accessing system properties (or maybe environment variables) e.g. as ${syspropname} within logstash.conf.