---
title: Processors
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Observability Pipelines > Processors
---

# Processors

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site). ().
{% /alert %}

{% /callout %}

## Overview{% #overview %}

{% alert level="info" %}
The processors outlined in this documentation are specific to on-premises logging environments. To parse, structure, and enrich cloud-based logs, see the [Log Management](https://docs.datadoghq.com/logs/log_configuration/logs_to_metrics) documentation.
{% /alert %}

Use Observability Pipelines' processors to parse, structure, and enrich your logs and metrics (Preview (PREVIEW indicates an early access version of a major product or feature that you can opt into before its official release.)). When you create a pipeline in the UI, pre-selected processors are added to your processor group based on the selected template. You can add additional processors and delete any existing ones based on your processing needs.

Processor groups are executed from top to bottom. The order of the processors is important because events are checked by each processor, but only events that match the processor's filters are processed. To modify the order of the processors, use the drag handle on the top left corner of the processor you want to move.

**Note**: For a pipeline canvas, there is a limit of 25 processors groups and a total of 150 processors.

Select a processor in the left navigation menu to see more information about it.

## Processors{% #processors %}

These are the available processors:

{% tab title="Logs" %}

- [Add Environment Variables Processor](https://docs.datadoghq.com/observability_pipelines/processors/add_environment_variables/)
- [Add Hostname Processor](https://docs.datadoghq.com/observability_pipelines/processors/add_hostname/)
- [Custom Processor](https://docs.datadoghq.com/observability_pipelines/processors/custom_processor/)
- [Deduplicate Processor](https://docs.datadoghq.com/observability_pipelines/processors/dedupe/)
- [Edit Fields Processor](https://docs.datadoghq.com/observability_pipelines/processors/edit_fields/)
- [Enrichment Table Processor](https://docs.datadoghq.com/observability_pipelines/processors/enrichment_table/)
- [Filter Processor](https://docs.datadoghq.com/observability_pipelines/processors/filter/)
- [Generate Metrics Processor](https://docs.datadoghq.com/observability_pipelines/processors/generate_metrics/)
- [Grok Parser Processor](https://docs.datadoghq.com/observability_pipelines/processors/grok_parser/)
- [Parse JSON Processor](https://docs.datadoghq.com/observability_pipelines/processors/parse_json/)
- [Parse XML Processor](https://docs.datadoghq.com/observability_pipelines/processors/parse_xml/)
- [Quota Processor](https://docs.datadoghq.com/observability_pipelines/processors/quota/)
- [Reduce Processor](https://docs.datadoghq.com/observability_pipelines/processors/reduce/)
- [Remap to OCSF Processor](https://docs.datadoghq.com/observability_pipelines/processors/remap_ocsf/)
- [Sample Processor](https://docs.datadoghq.com/observability_pipelines/processors/sample/)
- [Sensitive Data Scanner Processor](https://docs.datadoghq.com/observability_pipelines/processors/sensitive_data_scanner/)
- [Split Array](https://docs.datadoghq.com/observability_pipelines/processors/split_array/)
- [Tags](https://docs.datadoghq.com/observability_pipelines/processors/tag_control/logs/)
- [Throttle](https://docs.datadoghq.com/observability_pipelines/processors/throttle/)

{% /tab %}

{% tab title="Metrics" %}

- [Filter](https://docs.datadoghq.com/observability_pipelines/processors/filter/)
- [Tag Control](https://docs.datadoghq.com/observability_pipelines/processors/tag_control/)

{% /tab %}

## Processor groups{% #processor-groups %}

{% alert level="info" %}
Configuring a pipeline with processor groups is only available for Worker versions 2.7 and later.
{% /alert %}

{% image
   source="https://datadog-docs.imgix.net/images/observability_pipelines/processors/processor_groups.94ef017e75d60aa47838ee201bc0d31b.png?auto=format"
   alt="Your image description" /%}

You can organize your processors into logical groups to help you manage them. Each processor group has a Group Filter so that those processors are only applied to specific events. For example, if you want the group processors to only process events coming from `vpc`, then use the group filter `source:vpc`. You can also add filters for each individual processor.

Processor groups and the processors within each group are executed from top to bottom. The order of the processors is important because events are checked by each processor, but only events that match the processor's filters are processed. To change the order of the processors, use the drag handle on the top left corner of the processor you want to move.

**Note**: There is a limit of 25 processor groups per pipeline canvas. For example, in a dual-ship pipeline with two destinations, the combined number of processor groups across both destinations cannot exceed 25. You can have the groups in any combination, such as 15 on one destination and 10 on the other.

## Further Reading{% #further-reading %}

- [Rehydrate archived logs in any SIEM or logging vendor with Observability Pipelines](https://www.datadoghq.com/blog/rehydrate-archived-logs-with-observability-pipelines)
- [Transform and enrich your logs with Datadog Observability Pipelines](https://www.datadoghq.com/blog/observability-pipelines-transform-and-enrich-logs/)
