# FORWARD
Forward rules are applied when the logs are routed to downstream destinations. In a nutshell, these are similar to Filter rules, but filter rules are applied when Apica Ascent receives the data. Forward rules are useful in case organizations want to retain all the generated logs in InstaStore but want to selectively forward the data to other destinations by ensuring total compliance.
Multiple forward rules can be configured for a log stream. The data gets forwarded only if all the rules are satisfied. Forward rules can be configured to forward selective fields, which also helps in reducing the data volumes to the downstream system.
### To Add A Forward Rule:
* Open the `Configure Pipeline` page of the desired pipeline. To know more about creating and editing pipelines, [click here](https://docs.apica.io/flow/pipeline-management/data-flow-pipelines-new).
* Hover over the `+ Add Rule` button.
* Select `Forward` from the rule type dropdown.
* A form organized into tabs should be created in the `Pipeline Configuration` section of the page.
* Enter the name and select a group for the Forward rule.
Navigate to the `Forward Labels` tab, click on the `Forward Labels` toggle and select the fields that need to be forwarded. In this case, only the selected fields get forwarded.
### Rename Attributes:
This feature allows the user to rename the log attributes before forwarding it to any destination.
> Attribute is a piece of information which determines the properties of a field or tag.
{% hint style="info" %}
Renaming log attributes will only work when logs are being forwarded to any destination.
{% endhint %}
\
You should use this feature if:
* You want to **increase cost savings**
* You want to **decrease the payload size** being forwarded
* You want to rename the labels to **maintain a set standard across teams**
* You want to rename the attributes to **enhance the readability**
**To Rename Attributes:**
* Click on the `Rename Labels` tab enable the `Rename Labels` option.
There are 2 ways to choose fields to rename:
1. Using regex. Mention a regex to match with the field and the replacing text to the regex match phrase
2. Explicitly mention the field name and the replacement text.
{% hint style="warning" %}
**NOTE:**\
You should make sure that multiple rules are not active on a similar namespace;, otherwise, both rules will be applied, which will result in duplicate data being forwarded.
{% endhint %}
