Skip to content

Clarify remapper processor #33577

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
estherk15 merged 2 commits into from
Dec 24, 2025
+19 −5
Merged

Clarify remapper processor #33577

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3875c9c
Clarify remapper processor
estherk15 Dec 24, 2025
1b87c6a
Apply suggestions from code review
estherk15 Dec 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 19 additions & 5 deletions content/en/logs/log_configuration/processors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,13 +287,27 @@

## Remapper

The remapper processor remaps any source attribute(s) or tags to another target attribute or tag. For example, remap `user` by `firstname` to target your logs in the Log Explorer.
The remapper processor remaps one or more source attribute(s) or tags to a different target attribute or tag. For example, you can remap the `user` attribute to `firstname` to normalize log data in the Log Explorer.

Constraints on the tag/attribute name are explained in the [attributes and tags documentation][5]. Some additional constraints, applied as `:` or `,`, are not allowed in the target tag/attribute name.
If the remapper target is an attribute, the processor can also try to cast the value to a new type (`String`, `Integer`, or `Double`). If the cast fails, the original value and type are preserved.

If the target of the remapper is an attribute, the remapper can also try to cast the value to a new type (`String`, `Integer` or `Double`). If the cast is not possible, the original type is kept.
**Note**: The decimal separator for `Double` values must be `.`.

**Note**: The decimal separator for `Double` need to be `.`.
### Naming constraints

Characters `:` and `,` are not allowed in the target attribute or tag names. Additionally, tag and attribute names must follow the conventions outlined in [Attributes and Aliasing][5].

Check notice on line 298 in content/en/logs/log_configuration/processors.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.oxfordcomma 

Suggestion: Use the Oxford comma in 'Additionally, tag and'.

### Reserved attributes

The Remapper processor **cannot be used to remap Datadog reserved attributes**.
- The `host` attribute cannot be remapped.
- The following attributes require dedicated remapper processors and cannot be remapped with the generic Remapper. To remap any of the attributes, use the corresponding specialized remapper or processor instead.
- `message`: Log message remapper
- `service`: Service remapper
- `status`: Log status remapper
- `date`: Log date remapper
- `trace_id`: Trace remapper
- `span_id`: Span remapper

{{< tabs >}}
{{% tab "UI" %}}
Expand Down Expand Up @@ -1084,7 +1098,7 @@
[2]: /agent/logs/advanced_log_collection/?tab=configurationfile#scrub-sensitive-data-from-your-logs
[3]: /logs/log_configuration/parsing/?tab=matchers#parsing-dates
[4]: https://en.wikipedia.org/wiki/Syslog#Severity_level
[5]: /logs/log_collection/?tab=host#attributes-and-tags
[5]: /logs/log_configuration/attributes_naming_convention/
[6]: /logs/search_syntax/
[7]: /integrations/guide/reference-tables/
[8]: /tracing/other_telemetry/connect_logs_and_traces/
Expand Down
Loading