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 | 736 | 113 | 44 | +122% |
| Observability | 16 | 3,012 | 601 | 171 | +15% |
| Kubernetes | 4 | 1,493 | 255 | 93 | -18% |
| Platform Engineering | 1 | 469 | 101 | 44 | +1% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.