Roadmap

On this page

Roadmap

Note

Items on this page are planned, not shipped.

Planned

ItemStatus
Tier 2 extension: Java collectorsPlanned. Needs a spike on module class loader parents.
Tier 3 extension: custom UI panelsPlanned. Will stay off behind ui.allowCustomPanels.
Compare two requests in HistoryPlanned.
Load the full detail of an earlier request from HistoryNot available in v1. History shows summaries only.
Components panelNeeds core to announce onComponentInvocation.
Cache hit and miss eventsNeeds core. Lens uses statistic differences today.
SOAP eventsNeeds core.
Bar on core error pagesNeeds the web context to announce onRequestFlushBuffer.
ORM SQL in QueriesBuilt, as an opt in integration that listens to bx-orm events (see ORM). 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. See 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 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. It has a status section that says what v1 implements.