News for hackers. Stuff that matters.

A comment on The Elastic Stack: Future of ELK Platform. Parent comment

Re:The Elastic Stack: Future of ELK Platform by Xylakant on Thursday February 18, 2016 @10:11AM (#11126257)
> isn't the point of `/etc//conf.d` directories generally that you have multiple config files?

Yes certainly. It's totally fine to place multiple config files there, I do as well. I split up my configs in the various outputs, inputs etc. It's just that logstash combines them to a single pipeline and does not run a pipeline per config file. Nginx doesn't run a webserver per config file either :).

It's certainly something that's unexpected and could be much better documented, but alas, I'm just a user :)

(and I do agree, your issue could have been handled much better, especially since it's not actually a bug)

[ Parent | on HN ]
Re:The Elastic Stack: Future of ELK Platform by clebio on Thursday February 18, 2016 @10:18AM (#11126322)
Awesome, thanks for the clarification. This might help (if I ever go back to using logstash at this point!).

Yeah, my point was more that they accepted my issue, but there's no action and there are more than 600+ other open issues. Seems Elastic is too busy branding and pushing breaking changes to their APIs.

I do sincerely appreciate your clarifications and comments on this one, though.

[ Parent | on HN ]