How to Use This Tool
Convert event rate, payload bytes, burst and compression into an ingest link budget. Daily log volume can fit storage while short incident bursts overwhelm agents, queues or the network path into the collector.
Why Log Ingestion Bandwidth needs more than a raw total
Measure serialized bytes before transport and compression; field counts alone do not predict bandwidth. For this page, the useful comparison is peak compressed bandwidth in mbps, not whichever input happens to be largest. The Log Ingestion Bandwidth result answers the decision in the heading and should not be reused as a score for a different workflow.
The exact Log Ingestion Bandwidth formula
Mbps equals events per second × bytes per event × burst × remaining size after compression × 8 ÷ 1,000,000. The visible fields are Average events per second, Average serialized event size, Peak burst multiplier and Measured compression savings. For Log Ingestion Bandwidth, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed peak compressed bandwidth in mbps may be arithmetically valid but operationally meaningless.
Interpreting peak compressed bandwidth in mbps
Keep sustained throughput above the estimate and size disk buffers for the duration of downstream throttling. The ten-percent comparison is deliberately narrow: it tests the influence of average events per second and is neither a forecast nor a confidence interval. Preserve the values used, their dates and the resulting decision so a later reviewer can reproduce why Log Ingestion Bandwidth supported the choice.
What this Log Ingestion Bandwidth model leaves out
Protocol framing, TLS, retries, batching, multi-region replication, sampling and event-size tails are excluded. That is where Log Ingestion Bandwidth stops being trustworthy. If an excluded factor could reverse peak compressed bandwidth in mbps, extend the model explicitly or use the authoritative account system instead of hiding the factor inside an unexplained adjustment.
Evidence and independent verification
The reference reviewed for Log Ingestion Bandwidth is OpenTelemetry — Logs data model. OpenTelemetry — Logs data model supports the named definition or rule but does not supply private values for peak compressed bandwidth in mbps. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.
Private, reproducible calculation
Log Ingestion Bandwidth runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Log Ingestion Bandwidth inputs away from the site's calculation server, while leaving the user responsible for detecting stale data or a changed platform rule. When an assumption changes, reopen OpenTelemetry — Logs data model and rerun the saved Log Ingestion Bandwidth scenario.
Sources & assumptions
Tool Spec v2 · verified 2026-08-22. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- OpenTelemetry — Logs data model (checked 2026-08-22)
Model assumptions
- Every input covers the same reporting period or cohort.
- Protocol framing, TLS, retries, batching, multi-region replication, sampling and event-size tails are excluded.
- The calculator uses only the visible fields and does not fetch account data.
