---
title: Roadmap
order: 1
description: What is planned for BxLens and how it relates to BX Insights.
icon: lucide:map
---

# Roadmap

!!! note
    Items on this page are planned, not shipped.

## Planned

| Item | Status |
|---|---|
| Tier 2 extension: Java collectors | Planned. Needs a spike on module class loader parents. |
| Tier 3 extension: custom UI panels | Planned. Will stay off behind `ui.allowCustomPanels`. |
| Compare two requests in History | Planned. |
| Load the full detail of an earlier request from History | Not available in v1. History shows summaries only. |
| Components panel | Needs core to announce `onComponentInvocation`. |
| Cache hit and miss events | Needs core. Lens uses statistic differences today. |
| SOAP events | Needs core. |
| Bar on core error pages | Needs the web context to announce `onRequestFlushBuffer`. |
| ORM SQL in Queries | Built, as an opt in integration that listens to bx-orm events (see [ORM](../panels/orm.md)). The SQL is free, like normal queries. The ORM page with statistics needs BoxLang+. |
| Panels from other modules (ORM, Redis, mail, AI, JDBC pools, Quick, qb, ColdBox, cbwire) | Ideas. |

The BIF call collector is shipped, see the [BIFs panel](../panels/bifs.md). See [Core gaps](../reference/events.md#core-gaps).

## Not implemented

- The `lensDumpHeap` BIF. Heap dumps are in the console System page, need BoxLang+ and are off by default. Thread dumps are in the console Threads page.
- The `bx:lens` component.
- A frozen feature split between free and BoxLang+. The split in [Licensing](../licensing.md#free-and-boxlang) is the current state and may change.

## Relation to BX Insights

Lens works on one server. The bar shows what one request did, right on the page. The console shows live requests, executors, tasks, JVM numbers and threads for that server.

BX Insights is the separate observability product. It is the answer for clusters, history over time and alerting.

Lens will not add cross-node views or a database. It keeps requests in memory and clears them on restart. With BoxLang+ or a trial it saves errors and reports to disk so they survive restarts. Besides that it writes only the saved bar layout, the saved settings changes and the audit log.

## Design spec

The original draft is at [Design spec](../design/api-spec.md). It has a status section that says what v1 implements.