...
https://bplmdemoappstg.blob.core.windows.net/libraries/LHO_VERSION/init_script.she.g.
https://bplmdemoappstg.blob.core.windows.net/libraries/2.713.21/init_script.sh
Step 2) Prepare storage path in Catalog Explorer
...
open Catalog Explorer
select schema:
main/defaultcreate volume:
bp-lakehouse-monitor
The catalog, schema and name of the volume are configurable and these are default values.
Users that own shared clusters should be granted access to the configured catalog, schema and volume configured for the init script to be loaded from.
Workspaces to be monitored should also be configured to access the configured catalog.
...
Step 3) Upload script to
/Volumes/main/default/bp-lakehouse-monitor/script/
...
/Volumes/main/default/bp-lakehouse-monitor/script/init_script.sh
Grant cluster owner Users Read Access to Volume
...
Click on the bp-lakehouse-monitor volume in ‘Catalog Explorer’
Select Permissions
Click on Grant
Select READ VOLUME and add ‘Account Users’ principal (a more narrow group of users that own shared clusters can be configured instead. The same group should also have access to the catalog and schema where the volume is created).
...
Click on Grant
The storage location backing the configured catalog and schema should be accessible from every workspace to be monitored.
Allow init script execution
Step 1) In Databricks
open Catalog
open Metastore details
open Allowed JARs/Init Scripts
add a new entry for
/Volumes/main/default/bp-lakehouse-monitor/script/init_script.sh
...
...
Click on the bp-lakehouse-monitor volume in ‘Catalog Explorer’
Select Permissions
Click on Grant
Select READ VOLUME and add ‘Account Users’ principal
Click on Grant
Unity Catalog Disabled
This configuration step is done automatically by LHO when LHO Telemetry Agent is updated.
...
/Workspace/bp-lakehouse-monitor/script/init_script.sh
Note: permissions to this file must be granted manually to All Users in the workspace!
...
Related articles