This should be added to the docs somewhere.
Describe the feature:
Usage of pipelines.yaml and to specify pipeline.id and path.
Describe a specific use case for the feature:
To be able to run multiple pipelines https://www.elastic.co/guide/en/logstash/current/multiple-pipelines.html
After declaring your pipelines, modify the config to point to the files:
logstashConfig:
logstash.yml: |
...
pipelines.yml: |
# This file is where you define your pipelines. You can define multiple.
# For more information on multiple pipelines, see the documentation:
# https://www.elastic.co/guide/en/logstash/current/multiple-pipelines.html
- pipeline.id: main
path.config: "/usr/share/logstash/pipeline/logstash.conf"
- pipeline.id: secondpipeline
path.config: "/usr/share/logstash/pipeline/secondpipeline.conf"
This is related to logstash documenation, not Helm chart, isnit?
It's in the helm chart, but the config is related to logstash.
Helm chart allow you to configure pipelines.yml, but pipeline.yml format is related to logstash, not Helm chart. What is your question/issue here?
It's just a suggestion to be added to the docs somewhere.
This is a really helpful issue as https://github.com/elastic/helm-charts/blob/7.9/logstash/values.yaml#L16 is worded in a way that is a bit misleading IMHO
@windowsrefund @teebu feel free to to add an example here https://github.com/elastic/helm-charts/tree/master/logstash/examples with a multi-pipelines values.yaml!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity since being marked as stale.
Most helpful comment
It's just a suggestion to be added to the docs somewhere.