MicroStrategy

Sifflet connects to MicroStrategy to show which dashboards and reports depend on the tables you monitor in your data warehouse. When an incident affects an upstream table, you see right away which MicroStrategy dashboards and reports are impacted, and from a dashboard you can trace the cubes and warehouse tables that feed it. For the full list of imported assets and metadata, see MicroStrategy Collected Data.

🚧

Beta

The MicroStrategy integration is in beta. Contact Sifflet support to share feedback or report an issue.

Lineage graph with MicroStrategy assets

Lineage graph with MicroStrategy assets

Permissions Required

Sifflet reads MicroStrategy metadata through the MicroStrategy REST API, with a dedicated MicroStrategy user that authenticates with a username and password (standard authentication). Sifflet only reads object definitions: it doesn't modify objects and doesn't read report or dashboard data.

PermissionUsed forRequired
Consumer security role, on every project to importList the projects, dashboards, and datasets the user can accessYes
Use Architect Editors privilegeRead the definitions of dashboards, reports, cubes, and tables through the REST API. Checked by Test Connection.Yes
Web use Metric Editor privilegeRead the definitions of dashboards, reports, cubes, and tables through the REST API. Checked by Test Connection.Yes
Web Report SQL privilegeRead the definitions of dashboards, reports, cubes, and tables through the REST API. Checked by Test Connection.Yes

Test Connection checks that the user has the three privileges on at least one project, and the Consumer role on at least one project. Sifflet imports every project the user can access.

At each refresh, Sifflet reads the definitions of all dashboards, reports, cubes, and tables through the MicroStrategy REST API. On large environments, the first run can take several minutes.

Requirements

Required Roles for Setup

  • In MicroStrategy: a user with administrator rights, to create a user and grant it security roles and privileges.
  • In Sifflet: a role that can create credentials in Integrations > Credentials and sources in Integrations > Sources.

Supported Versions and Editions

Sifflet supports MicroStrategy Cloud and self-hosted MicroStrategy environments that expose the MicroStrategy Library REST API (<LIBRARY_URL>/api). Sifflet authenticates with standard (username and password) authentication.

Network Access

Sifflet connects to your MicroStrategy Library from the internet: its URL must be reachable from the public internet.

  • IP allowlisting: if you restrict inbound traffic to your MicroStrategy environment (for example with firewall rules on a self-hosted server), allow the IP addresses of your Sifflet instance, listed in Settings > Integration Preferences.

Other Prerequisites

To see lineage from your warehouse tables to MicroStrategy cubes, reports, and dashboards, add the warehouses that MicroStrategy reads from as sources in Sifflet first. See Lineage for the supported warehouses.

Connect Sifflet to MicroStrategy

Step 1: Create a User in MicroStrategy

  1. In MicroStrategy, create a user dedicated to Sifflet with standard authentication. See the MicroStrategy documentation on creating a user.
  2. Grant the user the Consumer security role on every project that you want Sifflet to import.
  3. Grant the user the following privileges:
    • Use Architect Editors
    • Web use Metric Editor
    • Web Report SQL

Keep the username and password of this user for step 2.

Step 2: Add the MicroStrategy Source in Sifflet

  1. Go to Integrations > Credentials and create a credential with the username and password of the MicroStrategy user, in the following format:

    {
      "user": "<MICROSTRATEGY_USERNAME>",
      "password": "<MICROSTRATEGY_PASSWORD>"
    }
  2. Go to Integrations > Sources, click New source, and select MicroStrategy.

  3. Fill in the source fields:

    FieldDescriptionExample
    Source nameThe name of the source in SiffletMicroStrategy production
    HostThe full URL of your MicroStrategy Library, with https:// and the Library path, without /api and without a trailing slash. If your Library uses a custom path, enter the full custom path.https://company_name.microstrategy.cloud/MicroStrategyLibrary
    CredentialsThe credential created abovemicrostrategy-sifflet-user
  4. Sifflet imports every project the user can access: there is no scope to select in Sifflet. To exclude a project, don't give the user access to it.

  5. Click Test Connection, then save the source.

Saving the source starts a first run. You can follow its status and logs in the source details, and the assets appear in the Data Catalog when the run completes, typically within a few minutes depending on the size of your environment. For refresh frequency, scheduling, and other source operations, see Integrations Management.

Troubleshooting

Test Connection Reports Missing Privileges

Symptom: Test Connection fails with:

Missing privilege(s): <PRIVILEGE_NAMES>

or:

The user must have the Consumer role on at least one project.

Cause: the MicroStrategy user doesn't have one of the required privileges, or doesn't have the Consumer role on any project.

Fix:

  1. Grant the user the missing privileges and the Consumer role, as described in step 1.
  2. Click Test Connection again.

Did this page help you?