HTTP Log

Prerequisites

The log source should be able to send its logs to an endpoint, commonly called "LogPush". The log source should also be able to reach the agent over the network, so any firewall rules must be adjusted to allow TCP and HTTP traffic to flow to the configured IP address and port.

Request Format

The request body should be JSON for requests made to the HTTP log receiver.

Supported Platforms

Bindplane Agent: v1.39.0+

PlatformMetricsLogsTraces
Linux
Windows
macOS

Configuration

FieldDescription
Listen AddressSpecifies what IP address the receiver should listen on for logs being sent as POST requests.
HTTP PortSpecifies what port the receiver should use for listening for logs.
PathSpecifies a path the receiver should be listening to for logs. Useful when the log source also sends other data to the endpoint, such as metrics.
Enable TLSOption to configure the receiver's HTTP server to use TLS.
Cert File LocationLocal path to the TLS cert file.
Key File LocationLocal path to the TLS key file.

Example Configuration

Basic Configuration

For basic configuration, only the listen_address and http_port parameters are needed.

Web Interface

observIQ docs - HTTP Log Source - image 1

Standalone Source

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Source
3metadata:
4  id: http
5  name: http
6spec:
7  type: http
8  parameters:
9    - name: listen_address
10      value: '0.0.0.0'
11    - name: http_port
12      value: '12345'