logstash-input-http
logstash-input-http copied to clipboard
When using ingress in GCP, load balancing needs to detect the health of back-end services, and the health check component must receive a 200 status code. However, after the basic...
For Content-Type `application/json` the `json` codec is used by default. That is helpful, but with the introduction of ECS it creates an issue. If the target option on the codec...
Add an example using the additional_codecs setting to clarify what the document is stating about using two codecs and reinforce the codec setting's tie back to the Content-Type setting Thanks...
Hello, I've tried to implement the missing feature as mentioned on https://github.com/logstash-plugins/logstash-input-http/issues/117 I am still not sure how to handle the `content-type` header as it seems we're re-using the one...
Cleanup both ruby and shell scripts to match various linters' suggestions. Mostly using the new hash syntax, as well as small readability changes. Additionally, update gitignore to not accidentally add...
I use logstash http input module with nxlog client. Both applications does not support setting keep-alive timeouts. Nxlog uses hard-coded 300 seconds, logstash input http server uses hard coded 20...
- Version: 3.3.5 - Operating System: - Config File (if you have sensitive info, please remove it): ``` input { http { port => 9006 codec => plain { charset...
Currently, in order to support multiple users, it is necessary to implement multiple instances of the plugin on multiple ports or set up a proxy in front of logstash that...
Config file : `input{ stdin{} http{ host => "127.0.0.1" port => 8080 } } output{ stdout{ } file{ path => "op.txt" } }` While brought-up the filebeat using "logstash -f...
Currently only the http-output plugin supports json_batch. It would make sense that http-input would do so too. I'm currently sending a file with hundreds of jsons in it with no...