Transform logs, metrics, and spans before Dash0 stores them
Rename, mask, or delete attributes as Dash0 ingests your telemetry, without changing your instrumentation, and check the result on a sample record before you save.
Until now, renaming an attribute, masking a token, or pulling a value out of a log body meant changing your instrumentation or running the OpenTelemetry Transformation Language (OTTL) in your own collector.
Now SignalControl, the rule-based pipeline your telemetry passes through in Dash0, has a Transform stage for logs, metrics, and spans. Its rules rename, set, delete, move, copy, extract, or mask attributes, or run your own OTTL, on every record that matches their condition.
In the rule editor, you pick a sample record from your telemetry, import one, or create one, and the Output panel shows what the rule changes in it before you save. Agent0, the Dash0 AI assistant, can suggest an extraction pattern from your sample values or propose the OTTL for each step, if your organization has it turned on.
Good to know
- In the log or span explorer, click Transform above the results to open a new rule with your current filter as its condition.
- Rules run in Dash0 on telemetry from every source, including what your SignalControl Edge collectors forward.
- Rules run before Dash0 enriches telemetry for storage, so they can't read the attributes it adds.
- Samples from your telemetry come from SignalStore, so they can include attributes Dash0 added during enrichment, which rules can't see.
Read the docs: About Signal Transformation