liveBook · Manning

Sidecar process

As explained in LLMs in Production

A sidecar is a companion component deployed alongside a primary application to perform supporting processing or communication.

A sidecar is a companion component deployed beside a primary application. For LLM services, it moves monitoring and log processing out of the inference path, avoiding unnecessary latency on good requests while still capturing quality and safety signals. section 6.2.5

A practical sidecar arrangement:

  • Runs a logging container in the same Kubernetes pod as the main application. section 6.2.5
  • Processes monitoring data in parallel rather than adding expensive checks to the critical path. section 6.2.5

LLM text monitoring

A whylogs sidecar with LangKit metrics can evaluate incoming prompts and generated text for readability, complexity, and toxicity, while the primary inference service continues serving requests. section 6.2.5

How LLMs in Production covers it

How deep it goes
Explains the same-pod logging pattern and its latency rationale, but does not detail alternative sidecar configurations.
Examples
Uses whylogs, LangKit, fluentd, WhyLabs, and Prometheus in a Kubernetes logging arrangement.
What you can do after
Operate/configure parallel monitoring for an LLM service using a Kubernetes sidecar and logging tools.
How it connects
Connects Kubernetes, monitoring, logging, inference paths, latency, and data quality checks.

Also explained in

Compare how 11 books explain sidecar process →

Related concepts

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