liveBook · Manning

Http_server

As explained in Logs and Telemetry

http_server is a Fluent Bit configuration attribute that enables its embedded web server.

http_server enables Fluent Bit’s embedded web server from the [SERVICE] block. It provides an HTTP interface for health checks, configuration inspection, and operational metrics. section 2.6 section 5.3.1

Configure the server alongside its network and monitoring options:

  • Set http_server to on to activate the server; use http_listen and http_port to choose its listening address and port. section 2.6 section 5.3.1
  • Enable health_check to make health responses reflect output-plugin errors and failed retries during the hc_period window. section 2.6
  • Enable storage.metrics when plugin metrics are needed through the API; the metrics include record throughput and data volume. section 5.3.1

Enable the local API

[SERVICE] flush 1 http_server on http_port 2020 health_check on hc_period 60 Query the server with curl 0.0.0.0:2020 or check health with curl 0.0.0.0:2020/api/v1/health.

How Logs and Telemetry covers it

How deep it goes
Explains service-block activation, listener settings, health thresholds, and metric collection, but does not detail endpoint responses exhaustively.
Examples
Uses a port-2020 service configuration and curl requests to the root and /api/v1/health endpoints.
What it assumes
Assumes familiarity with Fluent Bit service-block configuration and output plugins while demonstrating server activation from configuration basics.
What you can do after
Operate Fluent Bit’s HTTP API and interpret health responses based on output errors and retry failures.
How it connects
Connects HTTP APIs with health checks, output plugins, plugin metrics, storage metrics, and the Prometheus exporter.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Logs and Telemetry. The section links point to the parts of the book it draws on.