MicroStrategy

Nistor connects your BI layer to the warehouse underneath it, so a late table shows up as a late dashboard before anyone opens it.

What Nistor collects

• Assets: cubes, dossiers, reports, schedules, subscriptions and users.
• Lineage from dossier to cube to warehouse table, in BigQuery and in SAP HANA (SAP HANA tables are recognised from the SQL MicroStrategy runs).
• Events: refreshes and schedule runs on the activity timeline.
• Cost, with FinOps (Enterprise): the BigQuery spend behind each cube, report and dashboard, and cubes that refresh more often than they are used.
• Checks on the BI layer itself (cubes, dashboards and their refreshes), with Data quality (Enterprise).

What it can run

Refreshes follow upstream data readiness instead of fixed clock times: a rule refreshes a cube or a report (incremental-refresh reports included), or fires a MicroStrategy event, once every table it reads has new data.

Set it up

Give Nistor a MicroStrategy service user with read access to the projects you want observed, and refresh rights where rules should act. Discovery uses the MicroStrategy Python SDK, an optional extra: install it where the compiler runs with pip install 'nistor-tool-microstrategy[sdk]'. The README in the repository lists the settings.