HTTP
When Redpanda Connect runs it kicks off an HTTP server that provides a few generally useful endpoints and is also where configured components such as the http_server input and output can register their own endpoints if they don’t require their own host/port.
The configuration for this server lives under the http namespace, with the following default values:
-
Common
-
Advanced
# Common config fields, showing default values
http:
enabled: true
address: 0.0.0.0:4195
root_path: /benthos
debug_endpoints: false
# All config fields, showing default values
http:
enabled: true
address: 0.0.0.0:4195
root_path: /benthos
debug_endpoints: false
cert_file: ""
key_file: ""
cors:
enabled: false
allowed_origins: []
basic_auth:
enabled: false
realm: restricted
username: ""
password_hash: ""
algorithm: sha256
salt: ""
The field enabled can be set to false in order to disable the server.
The field root_path specifies a general prefix for all endpoints, this can help isolate the service endpoints when using a reverse proxy with other shared services. All endpoints will still be registered at the root as well as behind the prefix, e.g. with a root_path set to /foo the endpoint /version will be accessible from both /version and /foo/version.
Enabling HTTPS
By default Redpanda Connect will serve traffic over HTTP. In order to enforce TLS and serve traffic exclusively over HTTPS you must provide a cert_file and key_file path in your config, which point to a file containing a certificate and a matching private key for the server respectively.
If the certificate is signed by a certificate authority, the cert_file should be the concatenation of the server’s certificate, any intermediates, and the CA’s certificate.
Enabling basic authentication
By default Redpanda Connect does not do any sort of authentication for the service-wide HTTP server. However, it’s possible to configure basic authentication with the basic_auth field. Passwords configured must be hashed according to the specified algorithm and base64 encoded, for some hashing algorithms you can do this using Redpanda Connect itself:
echo mynewpassword | rpk connect blobl 'root = content().hash("sha256").encode("base64")'
Endpoints
The following endpoints will be generally available when the HTTP server is enabled:
-
/versionprovides version info. -
/pingcan be used as a liveness probe as it always returns a 200. -
/readycan be used as a readiness probe as it serves a 200 only when both the input and output are connected, otherwise a 503 is returned. -
/metrics,/statsboth provide metrics when the metrics type is eitherjson_apiorprometheus. -
/endpointsprovides a JSON object containing a list of available endpoints, including those registered by configured components.
CORS
In order to serve Cross-Origin Resource Sharing headers, which instruct browsers to allow CORS requests, set the subfield cors.enabled to true.
Debug endpoints
The field debug_endpoints when set to true prompts Redpanda Connect to register a few extra endpoints that can be useful for debugging performance or behavioral problems:
-
/debug/config/jsonreturns the loaded config as JSON. -
/debug/config/yamlreturns the loaded config as YAML. -
/debug/pprof/blockresponds with a pprof-formatted block profile. -
/debug/pprof/heapresponds with a pprof-formatted heap profile. -
/debug/pprof/mutexresponds with a pprof-formatted mutex profile. -
/debug/pprof/profileresponds with a pprof-formatted cpu profile. -
/debug/pprof/goroutineresponds with a pprof-formatted goroutine profile. -
/debug/pprof/symbollooks up the program counters listed in the request, responding with a table mapping program counters to function names. -
/debug/pprof/traceresponds with the execution trace in binary form. Tracing lasts for duration specified in seconds GET parameter, or for 1 second if not specified. -
/debug/stackreturns a snapshot of the current service stack trace.
Fields
The schema of the http section is as follows:
root_path
Specifies a general prefix for all endpoints, this can help isolate the service endpoints when using a reverse proxy with other shared services. All endpoints will still be registered at the root as well as behind the prefix, e.g. with a root_path set to /foo the endpoint /version will be accessible from both /version and /foo/version.
Type: string
Default: "/benthos"
debug_endpoints
Whether to register a few extra endpoints that can be useful for debugging performance or behavioral problems.
Type: bool
Default: false
cors.allowed_origins
An explicit list of origins that are allowed for CORS requests.
Type: array
Default: []
basic_auth
Allows you to enforce and customise basic authentication for requests to the HTTP server.
Type: object
basic_auth.password_hash
Hashed password required to authenticate. (base64 encoded)
Type: string
Default: ""