> For the complete documentation index, see [llms.txt](https://docs.krystal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.krystal.app/products/farms/track-farming-performance.md).

# Track Farming Performance

Krystal tracks trading fees and farming rewards separately, allowing you to understand how each source contributes to the position’s performance.

You can review both the current farming position and its historical results from the Auto-Farm Vault.

### View current position performance

Open the Auto-Farm Vault and locate the farming position.

The position table displays metrics including:

* Current liquidity
* Profit and loss
* Unclaimed rewards
* APR
* Price range
* Position status

Use these metrics to evaluate the current state of each farming position.

### View the yield breakdown

Hover over **Daily yield** to view the position’s earnings breakdown.

The breakdown includes:

* **Accumulated fees:** Trading fees generated by the LP position.
* **Farm reward generated:** Incentives earned from the underlying farming protocol.

This separation helps identify whether the position’s yield comes primarily from pool trading activity or farming incentives.

<figure><img src="https://1670507844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAmo4vXpjHKQh32RAZ0AA%2Fuploads%2FpxcpG7ZGMpUDwJbqqDVT%2FScreenshot%202026-07-31%20at%2014.30.01.png?alt=media&amp;token=8b04e997-589a-4efc-9558-ac5976874845" alt=""><figcaption></figcaption></figure>

### View historical performance

Open the vault’s **Overview** tab and locate **Historical Performance**.

You can switch between:

* **APY**
* **TVL**

Available time ranges include:

* 24 hours
* 7 days
* 30 days
* 90 days
* 1 year

When viewing performance, hover over a point on the chart to inspect information for that period.

The chart may display:

* APR or APY
* Trading fees earned
* Farming rewards earned
* Vault TVL

<figure><img src="https://1670507844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAmo4vXpjHKQh32RAZ0AA%2Fuploads%2FdP885YVn9sh31jmUbHP6%2FScreenshot%202026-07-31%20at%2014.30.49.png?alt=media&amp;token=8f7763ae-2783-4aba-b201-8466a483aa35" alt=""><figcaption></figcaption></figure>

### Understand performance changes

Farming performance can change because of:

* Trading-volume changes
* Pool-liquidity changes
* Reward-emission changes
* Reward-token price changes
* Position price-range changes
* Time spent in or out of range
* Position-management transactions
* Gas and execution costs

Recent APR and earnings should be treated as estimates rather than guaranteed returns.

### Evaluate each source of yield

When reviewing a farming strategy, consider trading fees and farming rewards independently.

High farming incentives may increase the displayed APR, but those incentives can decrease or end. Trading fees depend on the pool’s trading activity and the position’s active liquidity range.

Review the position regularly or configure supported automations and Agent instructions based on your strategy.


---

# 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.krystal.app/products/farms/track-farming-performance.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.
