out_http
Output plugin writes records via HTTP/HTTPS.@type
http
.endpoint
https
prefix.endpoint
parameter supports placeholders, so you can embed time, tag and record fields in the endpoint. Placeholders also require the buffer section in order to work. Here is an example:http_method
proxy
content_type
Content-Type
for HTTP request. out_http
automatically set Content-Type
for built-in formatters when this parameter is not specified.json
with json_array false
: application/x-ndjson
json
with json_array true
: application/json
csv
: text/csv
tsv
, ltsv
: text/tab-separated-values
msgpack
: application/x-msgpack
out_file
, single_value
, stdout
, hash
: text/plain
json_array
json_array
as true, Content-Type should be application/json
and be able to use JSON data for the HTTP request body.json_array true
json_array false
<format>
Directive@type
is json
.single_value
example:headers
headers
.open_timeout
read_timeout
ssl_timeout
tls_ca_cert_path
tls_client_cert_path
tls_private_key_path
tls_private_key_passphrase
tls_verify_mode
tls_version
tls_ciphers
error_response_as_unrecoverable
UnrecoverableError
when the response code is not SUCCESS, 1xx/3xx/4xx/5xx. If false
, out_http
logs error message instead of raising UnrecoverableError
.retryable_response_codes
out_http
retries the buffer flush.<auth>
Sectionmethod
basic
.username
password
out_http
's request body depends on <format>
configuration. For example, the default setting generates newline delimited JSON like this:@type single_value
:out_http
and in_http
json
format with json_array
as true for out_http
configuration:in_http
configuration should be:msgpack
format:in_http
configuration should be:forward
plugin to communicate with two Fluentd instances due to at-most-once
and at-least-once
semantics for rigidity.