--- title: Http Server slug: telemetry-pipeline/http-server docTags: createdAt: 2025-04-21T00:45:58.630Z --- # HTTP Server Source Receive logs, metrics, and traces over HTTP using a built-in HTTP server. This source allows worker to expose an HTTP endpoint and ingest telemetry data pushed by external systems. It is commonly used for custom integrations, webhooks, and systems that do not support native streaming protocols. ## Ingestion Model - worker runs an embedded HTTP server - External producers send telemetry data via HTTP requests - Requests are decoded based on the configured codec - Successfully processed requests receive an HTTP success response - Failed decoding or processing returns an error response This model enables push-based telemetry ingestion and decouples producers from backend pipelines. ## Source Configuration Parameters ## sources.\.type **required** **string** Specifies the source type. - Must be set to http\_server ## sources.\.address **required** **string** Network address the HTTP server listens on. - Format: \:\ - Use 0.0.0.0 to listen on all network interfaces - Port must be available on the host ## sources.\.path **optional** **string** HTTP path used to receive incoming requests. - Only requests matching this path are accepted - Path matching is exact **Default** :::BlockQuote / ::: ## sources.\.method **optional** **string** HTTP method accepted by the server. - Common values: POST, PUT - Requests using other methods are rejected **Default** :::BlockQuote POST ::: ## sources.\.encoding **optional** **object** Defines how incoming HTTP request bodies are decoded into events. ### sources.\.encoding.codec **required** **string** Codec used to decode the HTTP request body. Supported codecs include: - json - text - syslog - gelf - avro - protobuf - influxdb - otlp - native - bytes The selected codec determines: - Event structure - Signal type (logs, metrics, traces) - Parsing behavior ## Framing Configuration Controls how multiple events are extracted from a single HTTP request body. ## sources.\.framing **optional** **object** Framing strategy applied before decoding. ### sources.\.framing.method **optional** **string** Framing strategy used to split the request body into individual frames. Supported methods: - bytes - newline\_delimited - character\_delimited - length\_delimited - octet\_counting - chunked\_gelf Each frame is decoded as a separate event. ### sources.\.framing.delimiter **optional** **string** Delimiter character used with character\_delimited framing. ### sources.\.framing.max\_frame\_length **optional** **unsigned integer** Maximum allowed frame size in bytes. - Prevents memory exhaustion from malformed payloads - Frames exceeding this size are dropped ## ## sources.\.response\_code **optional** **unsigned integer** HTTP status code returned on successful ingestion. - Allows compatibility with systems expecting non-default success codes **Default** :::BlockQuote 200 ::: ## TLS Configuration Enables HTTPS for secure ingestion. ## sources.\.tls **optional** **object** TLS configuration block. ### sources.\.tls.enabled **optional** **boolean** Enables or disables TLS. ### sources.\.tls.crt\_file **optional** **string** Path to the TLS certificate file. ### sources.\.tls.key\_file **optional** **string** Path to the TLS private key file. ### sources.\.tls.ca\_file **optional** **string** Path to the certificate authority file. - Used for client certificate validation ## Authentication ## sources.\.auth **optional** **object** Authentication configuration for incoming HTTP requests. ### sources.\.auth.strategy **optional** **string** Authentication strategy. Supported strategies: - basic - bearer - custom ### sources.\.auth.username **optional** **string** Username for Basic authentication. ### sources.\.auth.password **optional** **string** Password for Basic authentication. ### sources.\.auth.token **optional** **string** Bearer token required in the Authorization header. ## Request Limits and Protection ## sources.\.max\_request\_bytes **optional** **unsigned integer** Maximum allowed size of an HTTP request body. - Requests exceeding this limit are rejected ## sources.\.request\_timeout\_secs **optional** **unsigned integer** Maximum time allowed to receive and process a request. - Protects against slow or stalled clients ## Metadata Enrichment Each event can be enriched with HTTP-specific metadata, including: - Client IP address - HTTP headers - Request path - HTTP method These fields enable: - Source attribution - Routing decisions - Auditing - Security analysis ## Multi-Signal Support The HTTP Server source supports: - **Logs** - **Metrics** - **Traces** Signal type determination depends on: - Selected codec - Payload structure - Framing configuration ## Common Use Cases - Custom application log ingestion - Webhook-based integrations - OTLP ingestion over HTTP - Lightweight telemetry gateways - Push-based observability pipelines