> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/k2k/2.0.0/k2k-offset-mapping/group-filtering.md).

# Group Filtering

By default, the K2K Offset Mapping App synchronizes all consumer groups for which offset mappings exist for at least one replicated topic. \
As such, no additional filtering is required for standard deployments.

<details>

<summary>Example</summary>

Given the consumer groups:

* &#x20;`fraud-detection-app`
* &#x20;`metrics-collection-app`&#x20;

If both have committed offsets for the topic `card-transactions`, and that topic is being replicated by K2K, the Offset Mapping App will translate and sync their committed offsets.

</details>

{% hint style="warning" %}
In order for the consumer offset mapping functionality to work, both of the following requirements must be met:

* K2K must be configured to publish offset mappings.
* The `k2k-offset-mapping` application must be configured and deployed.

Without both components active, consumer group offsets on the target cluster will not be translated.
{% endhint %}

This behavior can be customized in two ways:

* **Regex Pattern:** A regular expression can be provided to select only the consumer groups whose names match the pattern. This is useful for targeting a specific subset of groups based on a naming convention.
* **Explicit List:** A static list of consumer group names can be provided to restrict synchronization to only those specific groups.

## Regex Filtering

When used, only the groups matched by the provided regular expression will be synced.

```yaml
groups:
  consumerGroups: "transactions-.*"
```

## Explicit List

When used, only the groups present in the list will be monitored and synced.

```yaml
groups:
  consumerGroups: 
    - transaction-monitoring-group
    - fraud-detection-group
```


---

# 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.lenses.io/latest/k2k/2.0.0/k2k-offset-mapping/group-filtering.md?ask=<question>&goal=<user_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.
