Coralogix has expanded its TCO Optimizer to support DPXL (DataPrime Expression Language) at ingest time, enabling fine-grained data routing based on any field in the event payload — not just application, subsystem, and severity. Previously, routing rules were limited to three broad label fields, forcing teams to overpay for low-value data or work around limitations by encoding routing intent into naming conventions. With DPXL at ingest, engineers can now write expressive filter conditions targeting nested keys, custom fields, Kubernetes dimensions, tenant IDs, and more. Policies evaluate top-to-bottom with first-match-wins logic, and the same syntax used in DataPrime Explore queries works directly in routing rules. A key constraint: routing evaluates before enrichment, so only fields present in the original event are available. The change positions DataPrime as a pipeline-wide language, not just a query-time tool.
Table of contents
Programmable routing changes the rconomics of observabilityThe old way: broad rules, blunt tradeoffsWhat changes with DPXL at ingestFrom source identity to data contentWhy this mattersGetting startedThe bigger shiftSort: