[1.4.0] Add remote HTTP output handler.

[hcpadkins]

Overview

This pull-request adds an initial remote HTTP output handler. This output handler allows collected logs to be submitted to a configured HTTP / HTTPS endpoint via HTTP POST in ND-JSON format.

Additionally, this pull-request resolves a small bug in the the filter_paths processor, which raises a KeyError when a configured path to drop does not exist. This is a minor bug which only occurs in very specific configurations.

This pull-request is in response to the ask from #47.

Handler Configuration

In order to maximise compatibility, this handler provides the following configuration options:

• GROVE_OUTPUT_REMOTE_HTTP_URL
  • Description: The URL to POST collected logs to.
  • Example: https://192.0.2.1/some/endpoint
• GROVE_OUTPUT_REMOTE_HTTP_HEADERS
  • Description: An optional set of pipe ('|') delimited HTTP headers, in 'key: value' format.
  • Example: Content-Type: application/something|Authorization: 1234abcdef=
• GROVE_OUTPUT_REMOTE_HTTP_RETRIES
  • Description: The number of times to attempt a POST before failing [default: 5].
  • Example: 10
• GROVE_OUTPUT_REMOTE_HTTP_TIMEOUT
  • Description: The amount of time before an attempted POST fails [default: 10s].
  • Example: 20
• GROVE_OUTPUT_REMOTE_HTTP_INSECURE
  • Description: Disables certificate verification (insecure!) [default: False]
  • Example: True