> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/jentis-dcp-elements/account-settings/traffic-filters/how-to-configure-a-traffic-filter.md).
# How To Configure a Traffic Filter
1. On the Traffic Filters page, click on “Add New Filter”:
2. Create a name for your filter so you can identify it easily afterward:
3. On Filter State, you can set your filter to be active or inactive, defining whether you want to apply the filter to incoming data
4. On IP Addresses Rules, you’ll define based on which rules you’ll exclude the traffic. There are two options available:
1. IP address equals - an exact match to an IP address. Example: 192.168.1.20
2. IP address is in range - using a CIDR notation. Example: 192.0.2.0/24
They work on a concatenated logic - this means that, for example, if you have three different rules defined, if any of these rules can be applied to the incoming IP address, it will be excluded;
5. After finishing your setup, click on the "Save" button to see the filter you created on the Traffic Filters page. These filters are not applied to the data shown in the Preview Mode, so you can still see your own data flowing into the system;
6. After creating the filter, you can also easily activate or deactivate it on the “Traffic Filters” page;
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.jentis.com/jentis-dcp-elements/account-settings/traffic-filters/how-to-configure-a-traffic-filter.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
