> 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/configuration-reference/record-tracing.md).

# Record tracing

Add source lineage headers to replicated records.

{% hint style="info" %}
This feature is **disabled by default**. Set the corresponding `features` toggle to `enabled` in your pipeline file for the behavior described on this page to take effect.
{% endhint %}

When a record lands on the target Kafka cluster, operators often need to know which source topic, partition, and offset it came from — especially during failover or migration debugging. Kafka does not attach lineage metadata by default, therefore we inject tracing headers at replication time.

Set `features.tracingHeaders: enabled` to write source topic, partition, and offset into record headers using the names under `tracing.headers`. Tracing headers are separate from metrics; for pipeline health, see [Observability](https://docs.lenses.io/latest/k2k/configuration-reference/observability.md).

## Prerequisites

* [License accepted](https://docs.lenses.io/latest/k2k/configuration-reference/licenses.md)
* [Kafka connectivity and authentication](https://docs.lenses.io/latest/k2k/configuration-reference/kafka-connectivity-authentication.md)
* [Topic selection and data routing](https://docs.lenses.io/latest/k2k/configuration-reference/topic-selection-and-data-routing.md) configured

## Example

```yaml
name: "my_pipeline"
features:
  tracingHeaders: enabled
source:
  kafka:
    common:
      "bootstrap.servers": "source:9092"
    consumer:
      "group.id": "my-k2k-group"
target:
  kafka:
    common:
      "bootstrap.servers": "target:9092"
tracing:
  headers:
    topic: "x-source-topic"
replication:
  - source:
      topic: "orders.*"
  - sink:
      topic: source
      partition: source
```

## Configuration keys

### Feature toggles

| Key                                 | Description                                                                                | Required | Default    | Used by    |
| ----------------------------------- | ------------------------------------------------------------------------------------------ | -------- | ---------- | ---------- |
| `features.tracingHeaders`           | Inject tracing headers on replicated records (`enabled`, `disabled`, or per header object) | No       | `disabled` | Replicator |
| `features.tracingHeaders.partition` | Inject source partition tracing header                                                     | No       | `disabled` | Replicator |
| `features.tracingHeaders.offset`    | Inject source offset tracing header                                                        | No       | `disabled` | Replicator |
| `features.tracingHeaders.topic`     | Inject source topic tracing header                                                         | No       | `disabled` | Replicator |
| `features.tracingHeaders.pipeline`  | Inject pipeline name tracing header                                                        | No       | `disabled` | Replicator |

### Header names

| Key                         | Description                      | Required | Default           | Used by    |
| --------------------------- | -------------------------------- | -------- | ----------------- | ---------- |
| `tracing.headers.partition` | Header name for source partition | No       | `__k2k_partition` | Replicator |
| `tracing.headers.offset`    | Header name for source offset    | No       | `__k2k_offset`    | Replicator |
| `tracing.headers.topic`     | Header name for source topic     | No       | `__k2k_topic`     | Replicator |
| `tracing.headers.pipeline`  | Header name for pipeline name    | No       | `__k2k_pipeline`  | Replicator |


---

# 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/configuration-reference/record-tracing.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.
