HTTP Recorder

Configure HTTP Recorder sidecar for log ingestion via HTTP/TCP protocols.

  less than a minute  

This page covers Helm values for the HTTP Recorder sidecar configuration.

Deprecation Notice: The HTTP Recorder feature is deprecated and no longer recommended for new deployments. Consider using alternative log ingestion methods such as the HTTP/S Source or other supported source integrations.

HTTP Recorder Properties - Enabled

Variable: httpRecorderProps.enabled

Description: Enable httpRecorder, a frontend layer which can consume logs with both http and tcp protocols. It is deployed as a sidecar for each pipeline. It dumps the incoming logs to filesystem (persisted via PVC) and agents grab from there.

Example: httpRecorderProps.enabled=false (for disabled)

HTTP Recorder Properties - Image

Variable: httpRecorderProps.image

Description: Specify the httpRecorder image and version tag.

Example: httpRecorderProps.image="gcr.io/edgedelta/httprecorder:latest"

HTTP Recorder Properties - Ingress

Variable: httpRecorderProps.ingress

Description: Configure ingress for httpRecorder if the k8s cluster already has nginx + cert-manager installed. Without ingress enabled you can directly send logs within cluster using http://ed-httprecorder-svc.{namespace}.svc.cluster.local:8080

Example: httpRecorderProps.ingress={class: nginx}

HTTP Recorder Properties - Port

Variable: httpRecorderProps.port

Description: Specify the httpRecorder port.

Example: httpRecorderProps.port=8080