# Concat

### Description

The Concat processor can be used to concatenate fields together into a single string.

### Supported Types

| Metrics | Logs | Traces |
| ------- | ---- | ------ |
| ✓       | ✓    | ✓      |

### Configuration

<table><thead><tr><th width="193.99609375">Field</th><th>Description</th></tr></thead><tbody><tr><td>Condition</td><td>A condition that determines when this processor is applied.</td></tr><tr><td>Source Field Type</td><td>The type of telemetry that contains the fields to be concatenated.</td></tr><tr><td>Source Fields</td><td>The telemetry fields to concatenate together.</td></tr><tr><td>Target Field Type</td><td>The telemetry field type where the concatenation result will be placed.</td></tr><tr><td>Target Field</td><td>The target field to place the concatenation result into. May only be blank if Body is selected for the Target Field Type.</td></tr><tr><td>Delimiter</td><td>The delimiter to place between the source fields when concatenating. Defaults to a space, but may also be empty.</td></tr></tbody></table>

### Example Configuration(s)

Concatenating a syslog message back together after it has been parsed into multiple pieces, and the timestamp changed using the Rewrite Timestamp processor.

**The original log body**

<figure><img src="https://1405008107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgmiOMzBfoNFwmKJFHMcJ%2Fuploads%2F696dBUrEDaOERbcGppFR%2FOld%20Body-Fin.png?alt=media&#x26;token=c5d5fcc7-c285-4357-856c-82b4e00faf70" alt=""><figcaption></figcaption></figure>

**The attributes created by parsing, and then rewriting the timestamp**

<figure><img src="https://1405008107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgmiOMzBfoNFwmKJFHMcJ%2Fuploads%2FaiCa78fl6ypKAsHokEhb%2FAttributes-Fin.png?alt=media&#x26;token=6427eedc-d9b0-4d93-8cd7-8b797d9582f7" alt=""><figcaption></figcaption></figure>

**The concat processor settings**

The delimiter here is set to nothing (the default space deleted) since the fields maintained their spacing from the parsing.

<figure><img src="https://1405008107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgmiOMzBfoNFwmKJFHMcJ%2Fuploads%2F0Z7aONutfBvZNVVfpVrU%2FConcat-Fin.png?alt=media&#x26;token=da8a3fb2-d150-491c-83a4-d1055a727326" alt=""><figcaption></figcaption></figure>

**The final result concatenated and placed back into the log body**

<figure><img src="https://1405008107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgmiOMzBfoNFwmKJFHMcJ%2Fuploads%2FFYlEooP1SIHG3ThCXRum%2FNew%20Body-Fin.png?alt=media&#x26;token=afbb9586-bb2d-4e5f-ab35-327039a3e20d" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bindplane.com/integrations/processors/concat.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.