Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop pipeline without deleting it, when using centralized pipeline management #10559

Open
lmtjalves opened this issue Mar 14, 2019 · 2 comments

Comments

@lmtjalves
Copy link

With Centralized Pipeline Management enabled in Logstash, it would be nice to be possible to stop a pipeline, created in Kibana Pipeline Management, without having to delete it. So that we can later start it without having to create it again.

@lmtjalves lmtjalves changed the title [Feature request/enhancement] Stop pipeline without deleting it, when using centralized pipeline management Stop pipeline without deleting it, when using centralized pipeline management Mar 14, 2019
@bphenriques
Copy link

👍

@assaf79
Copy link

assaf79 commented Apr 8, 2019

Have been working on a fix for this one.
aside from adding a switch in kibana to turn pipelines on and off,
there are a couple of ways to make this change visible to logstash itself:

  1. a boolean indexed as a new field in the .logstash index. this requires changing the index in the elastic codebase, and possibly upgrading the existing index in previous versions of ES.
  2. a boolean stored within the pipeline's settings. in this case logstash can either (a) filter using a script (as the field isn't indexed), or (b) filter returned pipelines in logstash's code.

#1 is cleaner, but I couldn't find any examples of how ES upgrades existing system indices during version upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants