graylog_http_gelf
Use case
Same GELF message as graylog_gelf_udp, sent as an HTTP POST instead of UDP - useful when UDP is blocked, or you want a real HTTP status/error back per send.
Configuration
outputs:
- name: graylog2
type: graylog_http_gelf
url: http://graylog.example.com:12202/gelf
http_code: 202 # expected status, 0 = don't check
# auth - only needed if this GELF HTTP input sits behind something that
# requires it (e.g. a reverse proxy); a raw Graylog GELF HTTP input
# typically needs none, so these are commented out by default:
#username: cmt
#password: xxxxxxx
#token: "Bearer xxxxxxxxxxxxxxxx" # takes priority over username/passwordtoken (if set) is sent verbatim as the Authorization header - no
prefix added for you. See
fields common to every HTTP-based output
for the rest (ssl_skipverify, http_proxy, timeout, prefix, fieldmap).
Output
Same fields as graylog_gelf_udp: one HTTP POST per result (no bulk mode), with the same per-call circuit breaker on a hard send failure.
Example
cmt --report --output graylog2 --debug