NANORI LENS / DATABASE ACTIVITY CAPTURE

Start where the database activity happens.

Capture activity at the database host and bring it into Nanori Oversight for monitoring and investigation.

Request a demo ↗
Conceptual database volume with selected records highlighted in orange.
01

Observe activity at the source.

Lens runs on the database host. Your application continues to connect to the database; captured traffic is sent to Oversight.

02

Connect capture to investigation.

Give analysts captured statements and the account, session, and connection context available for the supported capture path.

03

Evaluate the environment precisely.

Database engine, version, operating system, connection path, and encryption configuration all matter. Review the intended deployment with Nanori before rollout.

How it fits.

Nanori Lens captures database activity. Nanori Oversight turns that activity into monitoring, investigation, and audit evidence.

Capture coverage is specific to the engine and connection path. Encryption metadata and statement visibility are distinct; do not assume every encrypted connection is observable.

Read the solution brief ↗