pipeline.shutdown_timeout: per‑pipeline runtime configuration missing
Goal Determine whether Logstash can expose a per‑pipeline shutdown timeout that can be adjusted while the instance is running, rather than relying on the global pipeline.shutdown_timeout setting in logstash.yml or the pipeline configuration file. Constraints & Uncertainty The current implementation treats pipeline.shutdown_timeout as a global value, appl
logstash