lifecycle

A new TCP connection was accepted.

An HTTP request head was fully parsed.

An HTTP response was fully sent.

method is the HTTP request method (e.g. "GET"). Use the sentinel"unknown"on error/early-out paths where the method is not known, never the empty string — metrics key the http_requests_totalcounter on this label.

A streaming HTTP response started and remains open.

A streaming HTTP response ended.

The client closed the connection unexpectedly.

The TCP connection was closed (by either side).

Interface for consuming lifecycle events.

Implementations must be thread-safe — in free-threading mode, multiple workers (threads) will callrecord()concurrently.

Default collector — discards all events.

Zero overhead: therecord()method is an empty function body. Used when no observability is configured.

Thread-safe collector that buffers events for batch processing.

Events accumulate in an internal list. Callflush()to retrieve and clear the buffer, or register anon_flushcallback for automatic batch processing.

Thread-safe viathreading.Lock— safe for free-threading mode where multiple worker threads produce events concurrently.

Logs lifecycle events as structured JSON for production observability.

Converts lifecycle events into structured log entries with correlation IDs, durations, and rich context for debugging production issues.

Features:

• Logs slow requests when duration exceeds threshold
• Structured JSON output when log_format="json"
• Correlation via connection_id and worker_id
• Zero overhead when log level filters out debug logs
• Thread-safe for free-threading mode

Return a globally unique, monotonically increasing connection ID.

Thread-safe — uses a lock for correctness under free-threading.