Modules

On this page

Modules

The Modules page lists every module loaded into the runtime, including modules nested inside other modules. Use it to check what is installed, which version runs and whether a module activated.

The Modules page

Integrations

The top of the page lists the integrations: modules whose events Lens can show. Each row has the integration, its module, a status and a switch.

StatusMeaningSwitch
Not installedThe module is not loaded. The row says "Install bx-orm to enable".Disabled.
Available, offThe module is installed, Lens is not listening.An admin can turn it on.
OnLens listens to the module's events.An admin can turn it off.

The switch is live, saved with the other settings changes and written to the audit log (integration.change). A viewer, or console.readOnly, sees the status and cannot change it. The setting is collectors.<id>.enabled, off by default.

The Integrations section

The list

The left side has one row per module, sorted by name, with a filter box. Each row shows the name, the version and the state:

StateMeaning
activeThe module activated.
loadedThe module is registered but did not activate.
disabledThe module is turned off.

A module that sits inside another one shows in <parent> next to its name. The bx-ai module that ships inside Lens is an example.

The detail

Pick a row to see:

  • The description and the home URL.
  • The author, and when the module activated and how long it took.
  • The path on disk.
  • The public mapping, if the module has one.
  • The parent module for a nested module, and the nested modules for a parent.
  • The modules it depends on.
  • What it provides: functions (BIFs), components, member methods, interceptors and custom interception points. Each list shows up to 80 names.
Note

A module that core registers through the Java service loader, like Lens itself, may show empty function lists.

Settings

The page uses the modules collector, used only by this page. Turn it off with collectors.modules.enabled, or hide the page with tabs.hide. The Environment page has a shorter list of modules with name, version, state and path.