> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/integrations/processors/remove-xml.md).

# Remove XML

Removes the XML node(s) matching an XPath from an XML string. Use it to drop noisy or sensitive elements before parsing or forwarding. The output is the trimmed XML string.

### Supported Telemetry Types

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

Choose Telemetry Type picks one signal per processor instance. Add another instance to handle a second signal.

### Configuration

#### Basic Configuration

<figure><img src="/files/UvSiwn7ceYitAJ5hhKBF" alt="Bindplane docs - Remove XML - image 1"><figcaption></figcaption></figure>

**Selection**

| Parameter             | Type               | Required | Default   | Description                                                                            |
| --------------------- | ------------------ | -------- | --------- | -------------------------------------------------------------------------------------- |
| Choose Telemetry Type | Telemetry Selector | Yes      | Logs      | The signal this instance runs on: Logs, Metrics, or Traces (one at a time).            |
| XPath                 | String             | Yes      | —         | The XPath selecting the element(s) to remove. Applies to all selected telemetry types. |
| Condition             | OTTL Condition     | No       | *(empty)* | Remove only from records that match. Empty runs on every record.                       |

**Source and target fields**

| Parameter         | Type                                    | Required | Default   | Description                                                                                                                     |
| ----------------- | --------------------------------------- | -------- | --------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Source Field Type | Enum: Resource, Attribute, Body, Custom | Yes      | Attribute | Where the XML string is read from. **Body is logs-only.** Custom takes any OTTL path.                                           |
| Source Field      | OTTL Field                              | Yes \*   | —         | The field holding the XML. Bracket notation for nested fields. For a Body source, leave empty to use the whole body.            |
| Target Field Type | Enum: Resource, Attribute, Body, Custom | Yes      | Attribute | Where the trimmed XML is written. **Body is logs-only.**                                                                        |
| Target Field      | OTTL Field                              | Yes \*   | —         | Destination for the trimmed XML. Point it at the source to edit in place. For a Body target, leave empty to use the whole body. |

\* The **Body** field type is the exception: it's optional, and leaving it empty targets the entire body.

**Body is available for Logs only.** For Metrics and Traces, the field type options are Resource, Attribute, and Custom.

### Examples

#### Strip a noisy subtree before parsing

<figure><img src="/files/wJN53xvYxsSJTiHewsRg" alt="Bindplane docs - Remove XML - image 2"><figcaption></figcaption></figure>

#### Redact a sensitive element

<figure><img src="/files/qwWyoiELVLilFQDeYVIn" alt="Bindplane docs - Remove XML - image 3"><figcaption></figcaption></figure>

XPath predicates with quoted strings are entered as-is; embedded quotes are escaped safely when the config is generated.

### Configuration Tips

* Removing elements before **Parse Simplified XML** shrinks the resulting map and keeps it focused.

### Troubleshooting

#### Too much (or nothing) gets removed

Symptoms: the result keeps the element you wanted gone, or loses more than intended.

Solutions:

1. Validate the XPath against a sample document. A broad expression can match more nodes than expected; a too-narrow one matches none (a silent no-op).
2. Confirm the source holds valid XML and the Condition evaluates true.

### Standalone Processor

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Processor
metadata:
  name: remove-xml
spec:
  type: remove_xml
  parameters:
    - name: telemetry_types
      value: Logs
    - name: log_condition
      value: not IsMap(body)
    - name: xpath
      value: //RenderingInfo
    - name: log_source_field_type
      value: Body
    - name: log_body_source_field
      value: ""
    - name: log_target_field_type
      value: Body
    - name: log_body_target_field
      value: ""
```

### Related Resources

* [RemoveXML — OTTL function reference](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/ottl/ottlfuncs/README.md#removexml)

### Bindplane Resources

These XML and slice processors are designed to work together. Chain them to normalize, parse, and reshape XML end to end:

* [Convert XML Attributes To Elements](/integrations/processors/convert-xml-attributes-to-elements.md)
* [Convert XML Text To Elements](/integrations/processors/convert-xml-text-to-elements.md)
* [Insert XML Elements](/integrations/processors/insert-xml-elements.md)
* [Parse Simplified XML](/integrations/processors/parse-simplified-xml.md)
* [Slice to Map](/integrations/processors/slice-to-map.md)
* [Get XML](/integrations/processors/get-xml.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.bindplane.com/integrations/processors/remove-xml.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.