> 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-13-34-otel-collector.md).
# Day 13/34 OTel Collector
As discussed, transmitting trace, log, and metric data to the APM framework through the OTel Collector is crucial. The OTel Collector, an open-source component, serves as the central hub for collecting, processing, and forwarding observability data.
Several APM products and event bus providers have developed plugins for the OTel Collector project, enhancing its functionality on top of the open-source version. These plugins facilitate the understanding of tracing data by chosen backends, aiding in end-to-end tracing of messages within applications or event brokers.
The OTel Collector offers more than just data routing; it includes essential features like sampling, filtering, and batching:
* Sampling: OTel simplifies data sampling for applications by allowing the marking of a sample flag on the OTel trace structure. The Collector then filters data based on specified percentages or criteria, like error codes or latency, reducing costs and enhancing efficiency.
* Filtering: The OTel Collector can filter trace log content, reducing log sizes and preventing unnecessary data exposure.
* Batching: By grouping logs and sending them in batches to the APM framework, the Collector improves data transfer efficiency.
These features contribute to the OTel Collector's effectiveness in observability data collection. They offer better data control, noise reduction, and resource optimization, leading to improved overall efficiency and cost reduction.
## 🚀 Let's Connect Beyond GitBook!
If you found this article helpful, you can find more of my technical insights, daily discussions, and deep dives across these platforms:
* **Read more of my work:** Check out my articles on [dev.to](https://dev.to/stephen_tsoi_5b2c4055f3a9) and [Hashnode](https://stephentsoi.hashnode.dev/).
* **Join the daily conversation:** Connect with me directly on [LinkedIn](https://www.linkedin.com/in/stephen-tsoi-16309730/).
***
#### 📬 Stay Ahead of the Curve
Enjoyed this piece? I break down complex technical topics into bite-sized, actionable insights every week.
👉 **Subscribe to my** [**LinkedIn Newsletter**](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7487299517642612736) to never miss an update and get the latest articles delivered straight to your feed!
---
# 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-13-34-otel-collector.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.
