> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/opentelemetry/from-missing-events-to-complete-visibility-tracing-enterprise-transactions-with-opentelemetry/day-20-34-minimize-the-bandwidth-usage-sampling-on-the-event-bus.md).
# Day 20/34 Minimize the bandwidth usage – Sampling on the event bus
There are thousands of events per second, or billions daily, passing through the event bus. Each step’s span data includes more than just **trace ID** and **parent span** data. Assuming the event bus handles 100,000 event messages per second, and each event message generates 2 span data sets for each event process (receiving event, deleting event), with each span data size being 3KB, the event bus will generate 600MB (or 4.8Gb) of tracing data per second. This can significantly impact network bandwidth utilization, system performance, and cost. We can control the traffic from four areas: Admin Console Control, Queue-Level Control, Sampling Control and Customizing Span Content.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/opentelemetry/from-missing-events-to-complete-visibility-tracing-enterprise-transactions-with-opentelemetry/day-20-34-minimize-the-bandwidth-usage-sampling-on-the-event-bus.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
