Use OpenTelemetry with Observability Pipelines for vendor-neutral log collection and cost control
Blog post from Datadog
In today's complex, hybrid, and multi-vendor environments, DevOps and security teams are increasingly adopting OpenTelemetry (OTel) for telemetry data instrumentation to avoid vendor lock-in. However, OTel alone lacks advanced processing functions and volume control, leading to fragmented setups. Datadog Observability Pipelines address these gaps by supporting OTel as a logs source, enabling teams to collect, process, and route telemetry data while maintaining a vendor-neutral architecture. This integration allows for unified data collection with pre-ingestion volume control, parsing rules, and automatic handling of OTLP protobuf for simplified data manipulation. Observability Pipelines support open-source frameworks, offering out-of-the-box normalization to the Open Cybersecurity Schema Framework (OCSF) and providing advanced data transformation capabilities. This solution ensures teams can process and route data efficiently across both on-premises and cloud-native environments without disrupting existing workflows or compromising visibility, ultimately enabling organizations to manage growing data volumes while adhering to budget constraints and compliance requirements.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| OpenTelemetry | 28 | 609 | 94 | 39 | +191% |
| Observability | 16 | 2,534 | 521 | 146 | +9% |
| Kubernetes | 4 | 1,297 | 225 | 80 | -9% |
| Platform Engineering | 1 | 488 | 92 | 36 | +13% |