Weave defines ingested bytes as bytes that Weave receives, processes, and stores on your behalf. Ingested bytes include trace metadata, LLM inputs/outputs, and any other information you explicitly log to Weave. Ingested bytes don’t include communication overhead (for example, HTTP headers) or any other data that isn’t placed in long-term storage. Weave counts bytes as “ingested” only once, when it receives and stores them.
Data Capture