> 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/changelog/lenses-6.2/agent.md).

# Agent

{% updates format="full" %}
{% update date="2026-06-09" tags="fixed" %}

## 6.2.3

### **Fixed**

* Kafka ACLs. Fixed a bug which block the creation and listing of ACLs if the principal contained more than one `:` separator.
  {% endupdate %}

{% update date="2026-05-29" tags="improvements" %}

## 6.2.2

### Improvements

#### Tunable topic sampling poll parameters

Two new optional config keys let you tune the topic-type-detection sampling consumer per deployment:

* `lenses.interval.topic.sampling.poll-timeout-ms` — per-attempt Kafka poll timeout for the sampling consumer (default `2000`).
* `lenses.interval.topic.sampling.poll-attempts` — maximum poll attempts before giving up (default `3`).

Both defaults match the previously hard-coded values, so existing deployments are unaffected unless you opt in.
{% endupdate %}

{% update date="2026-04-29" tags="improvements,fixed" %}

## 6.2.1

### Improvements

#### Provisioning API in OpenAPI

The Provisioning API is now documented in the OpenAPI specification.

#### Logging

* **`TopicStatsWorker` log noise** during normal operation has been demoted from `INFO` to `DEBUG`, so production logs stay readable.
* **Better diagnostic logging for topic identification** when investigating JSON payload edge cases.

### Fixed

#### SQL on partial JSON payloads

When a SQL query joined or selected from a topic whose value was a JSON object missing some fields, the engine could fail to resolve a union struct type. The engine now matches by **subset** of fields instead, so partial JSON objects no longer fail the query.

#### Topics with unresolved Schema Registry references stay readable

If a topic's value or key referenced a schema that the agent could not yet resolve from the Schema Registry (for example during startup or when the registry was briefly unreachable), reads against that topic could fail. Marshaller construction is now deferred, so the rest of the topic remains readable while the registry catches up.

#### Schema listing no longer shows "NaN"

The Schemas listing in the Agent UI no longer renders "NaN" in place of a name when a schema lacks a numeric identifier.

#### Topic configs page adapts to small viewports

The topic configurations screen now lays out correctly on smaller screen sizes and viewports.
{% endupdate %}

{% update date="2026-04-29" tags="new,fixed" %}

## 6.2.0

### K2K App Metrics

#### **Per-topic throughput breakdown**

The Throughput card now shows bytes/s and records/s per topic for both Source and Target, rather than showing only totals. A search bar appears automatically when there are more than 5 topics.

#### **Lag distribution visibility**

The Health card header now displays P50, P90, and Max lag across all source partitions at a glance. Source partitions with lag above the P90 threshold are highlighted in the partition table, and each lag cell shows the partition's share of total lag on hover.

#### **Studio tab navigation**

Clicking a topic name or offset value in any K2K metrics table now opens a studio tab directly instead of reloading the page. The same applies to K2K app links in the Topics drawer and the error tooltip buttons on the app listing.

### Fixed

#### Enhanced JSON Handling for Union Record Types in SQL

This update for Lenses SQL Processors, dealing with JSON Kafka topics involving unions and nested records, addresses previous query failures. Optional fields missing from JSON are now treated as `null`, exact schema matches are prioritized, and specific error messages indicate the path and expected type of any missing required fields.

#### Kafka data read

Reading Kafka data through a SQL snapshot is based solely on the record context, not the schema known to Lenses. This approach resolves issues where data, written using the schema registry with subject naming strategies like RecordNameStrategy, or TopicRecordNameStrategy, doesn't encounter failures.
{% endupdate %}
{% endupdates %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lenses.io/latest/changelog/lenses-6.2/agent.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.