Oops sorry, no idea how I could have linked to the wrong directive, but the correct one here is client_body_buffer_size, not proxy_buffer_* which has to do with the response buffers. 👍 1 Author therebelrobot commented Dec 11, 2015 Ooooooh, ok, that makes sense then. I tweaked...
have dedicated server(s) that does buffering, parsing, and enriching. Preferably in this order, so data can be buffered if processing is too expensive. An example of this design is a centralized Logstash receiving data from a lightweight log shipper, such as Filebeat. have dedicated buffering...