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.

Sign up for GitHub

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

Jump to bottom

Raise LogStash::Configuration Error on bad per-URL keys #22

Open

andrewvc opened this issue Jul 19, 2016 · 1 comment

Labels

Contributor

andrewvc commented Jul 19, 2016

It seems that there's a lot of confusion as to which options get set at the root level for this mixin and which ones get set per-URL.

Currently 'extra' options specified per-URL do not generate any errors. They should.

andrewvc added the enhancement label

Member

ppf2 commented Jul 19, 2016

+1 and while we are at it, can we also clarify the documentation? Currently, its just a listing of all the possible options. It will be nice if we document this upfront and specify which one(s) are at the per-url level vs. root level (eg. https://www.elastic.co/guide/en/logstash/current/plugins-inputs-http_poller.html#plugins-inputs-http_poller-ssl_certificate_validation) :)

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