This section explains how to set up Datalogz Control Tower for your organization: connect your analytics platforms, invite your people, and scope what each group manages. For who does what during setup, see the Getting Started guide.

1. Create a connector

A connector links Control Tower to one of your analytics platforms. Set up one connector for each platform your organization uses. Control Tower supports Power BI, Tableau, Qlik Sense, Sigma, Spotfire, Databricks, and SharePoint. Once connected, Control Tower automatically ingests your analytics metadata and activates default monitors. No further configuration is needed to start seeing results.

2. Invite members

Invite the people who need access to Control Tower. What each member can see and manage is determined by the user groups and teams they belong to and the roles they hold.

3. Set up teams

Teams scope a subset of your analytics estate, such as your production Power BI workspaces or a set of Tableau projects. Scoping by team lets each group track the health of the content it owns, without noise from the rest of the estate.

4. Add members to teams

Add your invited members to the relevant teams. This gives them access to the assets, monitors, and alerts they are responsible for.

In Users and User Groups you manage who can sign in to Datalogz Control Tower and what they are allowed to do.

Users are the individuals with access. Each user holds a role that defines what they can view, edit, or configure.

User groups bundle permissions: assign a role to a group once and every member inherits it. This keeps permissions consistent and saves you from managing roles user by user.

Recommended approach:

1. Create user groups that mirror your teams or departments (for example, Finance Analysts or Marketing Ops).

2. Assign the appropriate role to each group.

3. Invite users and add them to their groups. You can wait until your Teams setup is finished before inviting users.

To invite someone, go to Settings > Users, click Invite Users, and assign their role, groups, and teams. Invitations are sent by email.

Microsoft Entra ID, formerly Azure Active Directory, is Microsoft's cloud identity and access management service. Connect it to Datalogz Control Tower and Datalogz maps the users in your inventory to the departments listed in Entra ID. You will see this department information throughout the inventory and in BI360.

Prerequisites

• You have a Service Principal with (read-only) access to Entra ID.

How to connect to Entra ID

1. Go to Settings > User Directory.

2. In the Entra ID card, click Set up directory.

3. Fill out the tenant, client ID and client secret.

1. Click Connect.

Teams scope Control Tower to a subset of your BI estate. A team is linked to a single BI connector and covers the platform contexts you select, such as your production Power BI workspaces or a set of Tableau projects. Each team gets its own monitors, inventory, and insights; for Power BI teams, BI Similarity (preview) is also available.

Group people into teams by domain (for example Finance or Marketing), by collaboration, or by access level (for example Executives or Global Admins). Team members see and manage the content their team owns.

Access Control.

Users and Groups can be added to a team so they can view and interact with that team’s monitors, alerts, and assets. Users with the BI Viewer and BI Admin roles can access all the teams as a member or admin, respectively.

This guide sets up the Sigma connector using OAuth client credentials (Client ID and Client Secret), Sigma's recommended method for application-level access to the Sigma REST API. Datalogz reads metadata only; it never accesses the data inside your workbooks.

You will complete four steps: confirm Admin access and API availability, identify your API base URL, generate client credentials, and create the connector in Datalogz Control Tower.

1. You must be a member of the Admin account type in Sigma to generate API client credentials.

2. Your Sigma plan must include API access. If you are unsure, ask your Sigma account team to confirm the API is enabled for your organization.

Sigma hosts customers across multiple clouds and regions, and the correct API base URL depends on where your organization is provisioned.

This guide sets up the Qlik Sense connector using virtual proxy with header authentication, a Qlik method that is straightforward to configure between trusted systems. Datalogz reads metadata only; it never accesses the data inside your apps.

You will complete two steps: create a virtual proxy in the Qlik Management Console, and create the connector in Datalogz Control Tower. NPrinting monitoring is an optional third step.

1. In the QMC, create a virtual proxy with header authentication. See Qlik's virtual proxy documentation for the detailed steps.

2. Note the following values; you will need them in Step 2:

This guide sets up the SharePoint connector, which inventories your SharePoint sites, document libraries, and Excel workbooks through the Microsoft Graph API. Datalogz reads metadata only; it never accesses the data inside your files.

There are two ways to authenticate. App mode (recommended) uses an application registration with client credentials. User mode signs in as a user via Microsoft's device-code flow.

1. in the Microsoft Entra portal. Note the Application (client) ID and Directory (tenant) ID.

2. Under API permissions, add the Microsoft Graph application permissions Sites.Read.All and Files.Read.All, and grant admin consent.

Asset mapping connects your BI assets to your organization's taxonomy: functions, sectors, business units, departments, or any other logical grouping. Once mapped, those groups power the BI360 widgets and the inventory, so health, usage, and cost roll up by the part of the business that owns the content.

Asset mapping is set up per BI platform: each connector gets its own mapping connection, such as Power BI Asset Mapping or Tableau Asset Mapping. For each one, you upload a CSV or XLSX file that maps that platform's assets (for example Tableau workbooks, views, and data sources) to your taxonomy, and choose the level to aggregate by, such as department. Each card shows the file in use, what it aggregates by, and the latest sync status.

1. Go to Settings > User Directory.

2. Open the Asset Mapping card for your platform and upload your mapping file (CSV or XLSX).

New to Datalogz Control Tower? This guide gets your organization productive in the first 15 minutes.

Your Datalogz team completes onboarding with you first. During that process they set up your log-in method, configure connectors to your BI environment, and help you select and enable the monitors you want running. If any of these are incomplete, contact your Datalogz team before proceeding.

Configuration happens in Settings, organized into three groups in the left navigation:

• Organization: people and how they are grouped for access and ownership.

• Connectors: links to your BI platforms and identity provider.

Datalogz uses two kinds of roles.

• Account roles apply across your whole account. They control who can manage users, connectors, settings, and shared catalogs.

• Team roles apply within a single team. They control who can see a team's data and who can configure the team.

A user can hold several account roles at once, either assigned directly or through a group. Their permissions add up. Team roles work the same way: if a user belongs to a team directly and through a group, they get the higher of the two roles.

Datalogz User The standard role for everyone in the account. A Datalogz User can sign in and access basic features. Everything else comes from the teams they're assigned to.

BI Viewer Read-only access to every team's data, plus account-wide BI360 definitions and analytics. BI Viewers cannot change team configuration. This role suits analysts and leaders who need to see everything without administering anything.

This page covers creating, viewing, and deleting teams. Each team is linked to a single BI connector and has its own monitors, inventory, and insights.

• Root Users can create and split teams. They can also invite members.

• Admins can create new teams and invite members.

• All users can belong to one or more teams.

Follow these steps to create a team and add users to it.

Recommended Roles and Licenses

We recommend to use a Creator license with the Site Administrator Creator role for the easiest setup and most complete ingestion result.

Other supported Roles and Licenses

Datalogz supports the following licenses:

• Creator License (recommended)

• Explorer License

Datalogz supports the following roles to connect to your Tableau site and harvest metadata:

• Administrator

• Explorer, with

First, make sure that the following settings are enabled in Settings > General:

• Data Management, which is required to run the Tableau Metadata API and give the Explorer user access to databases and tables.

• Automatically grant authorized users access to metadata about databases and tables

• Show complete lineage (default)

• Turn on Tableau Catalogue (only when you want to configure access on an asset to asset basis).

Next, give the Explorer access to Tableau projects:

• For large projects that change often, we recommend making the Explorer a project leader. This ensures that the Explorer can access all Tableau assets within the project, including databases and tables.

• For projects where project leader status cannot be given, make sure that the Explorer has view access to all assets within the project.

This guide sets up the Spotfire connector. Datalogz extracts Spotfire metadata directly from the underlying Oracle repository database; support for other repository database types is not available at this time. Datalogz reads metadata only.

Before you start

Have the following ready, and decide whether you will connect via hostname and Service Name/SID or via DSN:

• The hostname of the database server.

• A database username and password with access to the Spotfire repository.

• The Oracle Service Name or SID (for hostname connections) or the DSN.

• Optionally, the Oracle protocol (TCP or TCPS for SSL).

1. Sign in to Datalogz Control Tower and go to Settings > BI Connectors.

2. Click New Connector and select Spotfire.

3. Enter the connection details for your chosen method (see the parameter reference below), then click Connect.

4. Enter a Connector Name and select the snapshot frequency (for example Daily or Weekly).

For questions or help with this setup, contact support@datalogz.io.

Connect your Tableau Server or Tableau Cloud environment to Datalogz Control Tower.

Datalogz authenticates to Tableau with a direct-trust connected app, Tableau's recommended long-lived authentication method. You provide an administrative Personal Access Token (PAT), and Control Tower creates and configures the connected app for you on each site you select.

The setup wizard lets you choose, per site, between a connected app and a PAT. A connected app is the recommended option.

• An administrative Personal Access Token (PAT):

  • For a single site, a Site Administrator PAT for that site (for example, Site Administrator Creator on Tableau Cloud).

OAuth clients allow external applications to connect securely to Datalogz without using a user’s password. Currently, OAuth clients provide access to the Datalogz MCP server.

Each OAuth client belongs to your organization. MCP clients can access data from all active connectors in the organization; access is not limited by team membership.

You need the Account Settings Admin, BI Admin, or System Admin role to manage OAuth clients.

Setup goes fastest when the right people are involved from day one. Five roles play a part in setting up Datalogz Control Tower. Here is what each role owns, with a checklist of actions for each.

1. Security/Identity Lead

This individual or team manages your organization's identity and access control system, such as Microsoft Entra ID (formerly Azure AD). Their primary responsibility is to create and secure the credentials Datalogz will use to access your BI and data environments.

Checklists:

The (BI) Administrator is the primary point of contact for your Business Intelligence platform, such as Databricks, Power BI, Tableau, Qlik and Spotfire. They will confirm that the Datalogz platform can successfully connect to and scan your environment.

Checklists:

The Network Lead is responsible for managing your organization's network security, including firewalls and network policies. They will ensure Datalogz has the required access to communicate with your internal systems.

Checklist:

• Whitelist the necessary Datalogz URLs and/or IP addresses on your corporate firewall:

  • 3.16.88.123

• Confirm that there are no proxy or firewall restrictions that would prevent Datalogz from connecting to your BI and data platforms.

This individual manages your Snowflake data warehouse. Their responsibility is to create the dedicated user account for Datalogz and grant it the appropriate read-only access to your metadata.

Checklist:

• Create a new, dedicated read-only user for Datalogz within your data warehouse.

• Grant the Datalogz user the required read-only permissions to query the account usage and metadata views.

• If your organization has IP whitelisting for your data warehouse, add the Datalogz IP addresses to the allowlist.

Your dedicated Datalogz representative will be your guide through the entire process. They will provide the specific technical details, perform the initial scans, and support your team throughout the setup.

Checklist:

• Provide the required technical documentation for all setup steps.

• Confirm the URLs and IP addresses that need to be whitelisted.

• Validate the Service Principal and data warehouse credentials you provide.

• Schedule and perform the initial data scans.

Connect each of your BI platforms to Datalogz Control Tower once; everything else, from inventory to monitoring, follows automatically. This page is the starting point: pick your platform, see what to prepare, and know what to expect after connecting.

Choose your platform

Each platform guide lists exactly which credentials to prepare and which settings to apply. Have the right person from the Getting Started roles available; creating credentials usually requires an admin of the platform.

1. Create credentials in your BI platform. Your platform's guide shows how, step by step.

2. In Control Tower, go to Settings > BI Connectors, click New Connector, and select your platform.

3. Enter the credentials. Control Tower tests them before saving, so a typo never becomes a broken connector.

4. Name the connector, choose the sync schedule (for example Daily or Weekly), and scope what to monitor.

• The first sync builds your inventory, and default monitors activate automatically. Alerts begin appearing on the Home dashboard.

• Syncs run on the schedule you chose. You can trigger a manual refresh anytime from the connector's detail page, where you can also follow sync status and history.

• When a credential is about to expire (for example a client secret or personal access token), re-authenticate from the connector's detail page. We recommend setting expiry reminders when you create credentials.

• Check the connector's sync history and logs on its detail page; failed runs show which step went wrong.

• The most common causes are an expired secret or token, missing tenant settings (Power BI), a wrong API host (Sigma), or a firewall blocking Datalogz. The IP addresses to whitelist are in the Getting Started guide.

• Still stuck? Contact support@datalogz.io with the connector name and the time of the failed sync.

Connectors read metadata only. They never access the data inside your reports, dashboards, or files.

Two more connections enrich everything the BI connectors collect by tying it to your organizational structure:

Set up the user mapping with the Entra ID guide, and see Asset Mapping for the file format and upload steps.

This guide sets up the Power BI connector using a service principal, Microsoft's recommended method for automated, application-level access.

Datalogz reads metadata only. It calls Power BI's read-only admin APIs for workspace, report, dataset, refresh, datasource, and activity information. It does not read the data inside your reports, and it does not write anything back to your tenant. The separate setting that permits writes, Service principals can access admin APIs used for updates, is not required by this setup and should stay off.

You will complete four steps: register an application in Microsoft Entra, add it to a security group, allow that group in your Power BI tenant, and create the connector in Datalogz Control Tower.

You will need two people, or one person holding both roles: someone with Microsoft Entra admin rights to register the application and create the group, and a Fabric administrator to change the tenant settings, which is the role Microsoft requires for Admin API settings.

Step 1: Register an application in Microsoft Entra

1. Register a new application in the Microsoft Entra portal. Note the Application (client) ID and Directory (tenant) ID shown on the Overview screen; you will need both later.

2. Under Manage, select Certificates & secrets, then New client secret.

3. Enter a description and leave the expiry at the recommended 180 days. You can choose a different duration, but when the secret expires you will need to create a new one and re-authenticate the connector.

4. Click Add and copy the secret Value immediately. This is your Application Secret Value. It cannot be viewed again after you leave the page.

1. In the Microsoft Entra portal, with Group type: Security.

2. Enter a Group name. You will need it for the tenant configuration in the next step.

3. Under Members, search for the application you registered in Step 1, select it, and confirm. The application should now appear under Direct members.

1. From the Power BI admin portal, open Tenant settings:

   1. Under Developer settings, find Service principals can call Fabric public APIs, select Specific security groups, enter your security group, and click Apply.

   2. Under Admin API settings, do the same for each of the following: Service principals can access read-only admin APIs, Enhance admin APIs responses with detailed metadata, and Enhance admin APIs responses with DAX and mashup expressions.

1. Sign in to Datalogz Control Tower and go to Settings > BI Connectors.

2. Click New Connector and select Power BI.

3. Select Connect using a Service Principal (SP) and click Connect.

4. Enter the Directory (Tenant) ID, Application (Client) ID, and Application Secret Value

Capacity monitoring is optional but highly recommended if you run Premium or Fabric capacities. It lets Control Tower track capacity usage with the application you registered above.

1. In the Power BI admin portal, under Tenant settings > Integration settings, find Semantic Model Execute Queries REST API, select Specific security groups, enter your security group, and click Apply.

2. Install the : in Power BI, go to Apps, search for it and add it, then open the Microsoft Fabric Capacity Metrics workspace it creates, go to Manage Access, and grant Admin permissions to your security group. Run the app once to start data flowing.

3. Note the ID of the Fabric Capacity Metrics semantic model. You can find it in the URL when viewing the semantic model in your browser. Enter it in the capacity settings of your Power BI connector.

For questions or help with this setup, contact support@datalogz.io.

This guide sets up the Databricks connector using an account-level service principal with OAuth machine-to-machine (M2M) authentication. The Databricks connector brings your Databricks account into Datalogz Control Tower: workspaces, Unity Catalog assets, lineage, dashboards, and Genie agents, including how people actually use those agents.

Datalogz reads metadata only: names, owners, structure, lineage and usage of your Databricks assets. It never reads the data inside your tables, and it makes no changes to your Databricks account.

You need people with these roles in Databricks:

• Account admin, to create the service principal and give it the account admin role

• Workspace admin on each workspace you want monitored, to assign the service principal

Unity Catalog should be enabled on the workspaces you want monitored.

• Qlik Sense data in the Datalogz Control Tower comes from four sources: the QRS API, the Engine API, server audit logs, and the NPrinting API

• Together, the information from these sources paint a detailed picture about what resources are stored in the Qlik Sense and NPrinting environments and how they are used

• Metadata is aggregated across sources to generate comprehensive alerts and insights

Datalogz supports self-service SAML single sign-on, so an administrator can connect your identity provider directly, without a support ticket. This is part of Organizational Setup.

How to configure SAML SSO

1. Go to Settings > Single Sign-On.

2. Click Configure SSO.

3. Enter the SAML details from your identity provider: the Sign-in URL, Issuer / Entity ID, and the signing certificate.

4. Copy the Datalogz Assured Consumer Service (ACS) URL and Entity ID into your identity provider's SAML application.

5. Click Save to store the configuration, then use Test connection to confirm a successful round trip before rolling it out to users.

For users who are not signing in through SSO, Datalogz offers a passwordless email login. The user enters their email, receives a one-time code, and enters it to sign in. There is no password to set, store, or reset.

Administrators can show a configurable announcement banner on the login screen, for example to communicate planned maintenance or a change to sign-in. The banner is driven by configuration and appears to every user before they sign in.

For questions or help with this setup, contact support@datalogz.io.

A healthy analytics environment requires attention across five essential pillars: Security, Cost Management, Governance, Quality Standards, and Performance. Every monitor and alert in Datalogz Control Tower is tagged with one or more of these pillars, so you always know why an issue matters and who should care about it.

Security

Security is continuous oversight of who can access your BI environment and how it is being used. Control Tower flags risks such as unusual access activity, suspicious export behavior, and permission changes on sensitive assets.

What you do: review security alerts as they appear and route them to the right owner. High-visibility assets get extra protection automatically.

Cost Management

Cost Management is about getting full value from your BI investment without waste. Control Tower identifies unused licenses, idle reports and dashboards, redundant refreshes, and other avoidable spend across your BI tools.

What you do: review surfaced savings opportunities, confirm with asset owners, and clean up. Most customers surface measurable savings within the first weeks.

Governance

Governance keeps your analytics estate structured, owned, and compliant. Control Tower detects orphaned and unowned assets, uncertified content, stale reports, and policy breaches such as users outside your SSO standard. Control Tower finds duplicate measures, reports built without a proper data model, and conflicting or redundant content that leads to inconsistent answers across teams.

What you do: assign owners to unowned assets, certify the content your organization should trust, and retire what is stale. Consolidate duplicates and standardize on certified definitions so every team reports from the same source of truth.

Performance ensures reporting stays fast and reliable. Control Tower tracks failed and long-running refreshes, capacity pressure, and configuration issues before they slow your users down.

What you do: act on refresh and capacity alerts to keep dashboards loading and data fresh.

Control Tower ships with a catalog of curated default monitors for each connected BI platform (Power BI, Tableau, Qlik Sense, Sigma, and Databricks). Each monitor continuously checks your environment against a specific rule and is tagged with the pillar it protects. When an asset breaches a rule, an alert is created with the affected asset, the reason, and a recommended fix.

You can also create custom monitors to track rules specific to your organization, such as internal naming standards or department-specific thresholds.

Actions to take:

1. Open the Monitor Catalog and enable the monitors relevant to your environment. Default monitors work out of the box.

2. Subscribe the right people to monitor notifications so alerts reach owners immediately.

3. Triage alerts from the Alerts page: assign, prioritize, and resolve. Every change is tracked in an audit trail.

4. If a check you need is missing, create a custom monitor or request one from the catalog.

Refresh Analytics is a tab in on Power BI Workspace asset pages that shows a refresh heatmap of how many semantic models are refreshing according to their schedule and how long those refreshes take. It helps you quickly understand refresh reliability and performance at the workspace level.

Datalogz Control Tower

Every enterprise has data infrastructure. Almost none has decision infrastructure.

Decision infrastructure is the layer that makes sure every decision taken inside the company, whether it comes from a dashboard, a deck, a person, or an AI agent, is traceable, reliable, accurate, consistent, and reached by the cheapest path available. Your data catalog knows your tables. Your quality tool watches your pipelines. Neither one watches the consumption layer, where people and agents actually decide things.

Datalogz Control Tower is that layer. It reads and continuously monitors your entire analytics estate across every connected platform, and turns what it finds into work that has an owner and an end state.

These docs cover setting Control Tower up, using it day to day, and the reference material behind it.

Connected platforms: Power BI, Tableau, Qlik Sense, Sigma, Spotfire, SharePoint, Databricks (preview), and Entra ID for identity.

Start here

Setting Control Tower up for the first time

• Getting Started: who in your organization needs to be involved, and what each person does

• : connect your first BI platform

• : add members, set up teams, assign roles

• and

Your platforms are connected and you are looking at your estate

• : what has surfaced, and what to do with it

• : what Control Tower checks, and how to change it

• : every asset across every tool, with Lineage for what depends on what

• : the duplicate and conflicting reports your teams built separately and never reconciled

Two ideas hold the rest together.

Monitoring is continuous. Monitors check your connected platforms around the clock. When something needs attention, an alert is created, routed to an owner, and tracked until it is resolved. There is nothing to configure to begin: once a platform is connected, a curated set of core monitors starts running against it. Your team reviews what surfaces, assigns owners, and acts. Scanning, detection, routing, and tracking happen without you.

Every finding sits under one of four pillars. Security, Cost Management, Governance (which covers quality, ownership, and compliance), and Performance. The pillar tells you why a finding matters and helps you decide what to deal with first.

You don't need to configure anything to get started. Once your BI platforms are connected, Control Tower begins monitoring with a curated set of default checks. Your team's job is to review the alerts that surface, assign owners, and act on them. Everything else, including scanning, detection, and tracking, happens automatically.

To learn more about the operational discipline behind the framework, we recommend reading our.

On any alert, workflows whose filters match that alert appear as buttons.

To run a workflow:

1. Click the Run Workflow button on the alert page.

1. Fill in the required inputs: for Send Email, fill in a recipient and a comment.

1. Click Run.

The workflow executes immediately. A session record is created in the workflow's , showing the result of each step.

If required inputs are missing or invalid (for example, an unrecognized user), you'll see an inline error and the workflow will not run. No partial session is saved.

A monitor is a powerful tool designed to continuously track and evaluate the health and performance of your Business Intelligence (BI) assets. It uses a customizable SQL query to automatically scan your environment for assets that do not meet predefined standards or expectations, such as outdated datasets, underused reports, or security issues. Because monitors are highly customizable, you can edit the SQL query, assign statuses, and determine the team responsible for resolving triggered alerts. This makes them a highly efficient and scalable way to manage large sets of assets and ensure any issues are detected and handled effectively.

Our monitoring solution includes a set of default monitors to help you oversee your BI environment effectively. Should your organization require additional monitoring capabilities beyond these defaults, Datalogz can create custom monitors tailored to your specific needs. Additionally, you have the option to clone and modify existing monitors to better suit your individual requirements. These personalized monitors can be easily managed in the "My Monitors" section under the Monitor tab.

are pre-configured monitors designed to cover common and critical scenarios for BI cost, security, performance, and governance. They come with predefined thresholds and logic, ready to use out-of-the-box. They are useful to provide a baseline level of monitoring for all users, ensuring fundamental issues are detected automatically.

Custom Monitors are highly specific monitor configurations created by Datalogz based on your organization’s unique requirements, business processes, or data sensitivities. These monitors are tailored for a very specific use case within your environment and are not designed to be broadly shipped to other customers. Datalogz can create these monitors on your request and ship them as default monitors.

To extend monitoring capabilities beyond the defaults, addressing unique operational concerns, compliance requirements, or performance benchmarks specific to your BI usage, contact Datalogz.

You sign in to Datalogz Control Tower with the log-in method configured at your license activation. Control Tower supports the following methods.

Sign in by proving your email address. A code will be sent to your email with which you can access your Datalogz Control Tower.

SAML 2.0 single sign-on, including Okta, is available for enterprise accounts. Contact your Datalogz team to configure it.

This release introduces a major upgrade to the Datalogz platform, focused on making BI environments easier to monitor, govern, and optimize at scale.

We’ve redesigned core parts of the platform to:

• Deliver more actionable alerts with less noise

• Provide clear executive visibility into BI performance

• Enable stronger governance and operational workflows

• Lay the foundation for automation, lineage, and integrations

New executive-level views make it easier to understand BI performance at a glance.

• An which shows the BI health at a glance.

• New with a redefined KPI library (usage, cost, health, governance)

Result: Faster, clearer insights for business and executive stakeholders.

We’ve introduced the first version of to support operational processes.

• Visual + YAML builder: Drag-and-drop jobs on a canvas, or edit the same Workflow as YAML. Pick your view; they stay in sync.

• Send Email module: Send to a static address, a Datalogz Team, or the alert row's owner via {{owner}}.

• Manual steps: Pause a run until an approver clicks Approve on the Sessions tab.

Result: More consistent and scalable BI operations.

New lineage capabilities in provide visibility into how assets are connected.

• Understand upstream and downstream dependencies

• Trace relationships between datasets and reports

Result: Faster impact analysis and improved trust in your data.

We’ve completely rebuilt the monitoring and alerting system to help teams focus on what actually matters.

• Create and manage monitors easily

• Get cleaner, deduplicated alerts with improved grouping

• Support for event-based alerts in addition to asset-level issues

• Better visibility into alert history and context

Result: Fewer, higher-quality alerts and faster issue resolution.

We’ve redesigned how metrics are captured and analyzed.

• Clear distinction between current state and historical trends

• Improved performance and accuracy of metrics

Result: Better visibility into how your BI environment is evolving over time.

• Improved permissions and access control

• Expanded collections and tagging capabilities

• Continued rollout of similarity detection

• New APIs to expose core platform functionality

Result: More flexibility in organizing, governing, and integrating your BI environment.

Metric Explorer is the starting page of Semantic Intelligence. It shows the state of metric definitions for the selected connector and team, and lets you open any concept for the full comparison.

To open it, go to Semantic Intelligence in the left navigation.

Search business concepts

Type a concept name in Search business concepts. Suggestions appear as you type, each with its status, its source definition, and how many similar, drifting and conflicting definitions it has. Select a suggestion, or press Search to open the best match.

Explain this gives a plain-English answer about the concept you searched for, generated by an LLM. It requires the Semantic Intelligence AI add-on and is off by default. Without the add-on, the button is shown but disabled.

Key figures

The scorecard lists one row per business concept, with the most definitions first.

Sort or filter any column. Filtering Status on Conflicting and sorting by Consumers is a quick way to find the disagreements that reach the most reports.

Release date: October 28, 2026

This release gives you a deeper look inside Tableau data sources, extends Databricks Genie coverage, and tidies up the Inventory Summary, along with fixes to alert counts, Tableau lineage and BI Similarity.

What's New

• Tableau Data Attributes: Tableau data sources now have a Data Attributes tab listing their columns and calculated fields, so you can see what a data source contains without opening Tableau.

• Open in Tableau from every asset: Dashboards, worksheets and workbooks now show their Webpage URL, and every Tableau asset carries the Open in BI icon to jump straight to it in Tableau.

• Databricks Genie:

  • A benchmark monitor: A new predefined monitor, "Genie agents below benchmark", alerts you when a Genie agent falls below its expected performance.

  • Synonyms and token counts: The Genie agent panel now shows the synonyms defined for each agent, and Genie token counts are visible in the UI.

  • Inventory Summary: The Databricks inventory summary now includes Genie metrics, with drill-through to the assets behind each number.

• Richer Databricks inventory: Databricks assets now carry their domain, page and tags, which makes them easier to search, filter and organize.

• Cleaner Top Reports: Top Reports on the Inventory Summary no longer lists Power BI [App] copies next to their source reports, so each report shows up once. The Top Reports and Asset Growth sections also got small layout improvements.

• Active users over 90 days: Active users are now counted over the last 90 days (previously 30) for Power BI, Qlik and BI 360, which gives a fuller picture of who relies on your content. You can expect active-user numbers to be higher than in previous releases because of the longer window.

• Faster Alerts page: The Alerts page now loads faster on accounts with large alert volumes.

• Semantic Intelligence pipeline: Improvements to the Semantic Intelligence processing pipeline for more reliable results.

• Fixed the side panel "Active Alerts" count and team alert counts not updating after a monitor was removed.

• Fixed Tableau "Used by Workbooks" lineage, and dashboards now correctly show lineage to their published data sources.

Sigma monitors are pre-configured monitors to help you quickly begin monitoring common and critical aspects of your Sigma environment. For more information, see the Monitors documentation.

Control Tower ships 9 default Sigma monitors. Every monitor can be switched on or off in the Monitor Catalog, and cloned into My Monitors to tailor its logic.

• Broken Connections (Performance): data connections that are failing or no longer reachable.

• Broken Lineage (Quality Standards): workbooks or data models whose lineage references are broken.

• Direct User Grants

The Monitor Catalog is where you control which Datalogz monitors run for each BI platform. Every monitor is on by default.

What you do:

1. Go to Settings > Monitor Catalog.

2. Open the tab for your BI platform (Power BI, Tableau, Qlik Sense, Sigma, or Databricks).

3. Toggle individual monitors on or off. Monitors you switch off stop generating alerts.

4. If a check you need is missing, use the request a monitor option and the Datalogz team will follow up.

The catalog controls what is available account-wide; which monitors run for a specific team is set during team setup.

What's new

Control Tower now includes additional metrics to help you filter, sort, and quickly identify assets that require attention.

• Workspace asset counts You can now see the total number of assets within a Power BI workspace directly on the workspace asset page and in the workspace inventory table.

• Report usage metrics Power BI report pages and the report inventory table now display unique views, unique viewers, and download counts, giving you better insight into report adoption and business impact.

These enhancements make it easier to prioritize monitoring, governance, and cleanup efforts across your Power BI environment.

What's new

BI 360

We are excited to introduce BI 360, a revamped executive dashboard that delivers a complete 360 degree view of BI usage, adoption, and licensing across your organization. BI 360 brings together insights that were previously fragmented into one streamlined, executive ready experience.

BI 360 offers the following featues:

Cross Tool Insights

• Compare key asset layers across BI tools to understand where you have the most assets.

• Instant visibility into BI health at the tenant or server level

Global BI Inventory

• Centralized inventory of BI assets across connected tools

• Browse and search reports, dashboards, datasets, and folders from one place

• Foundation for deduplication and cleanup initiatives

• Power BI Inventory now includes Workspace-level insights with:

  • Workspace details

  • Refresh heatmap

• Improved filtering reliability across inventory views.

• Inventory filter issues resolved.

• Global Inventory search now refreshes correctly after clearing search terms.

• Fixed inconsistencies in alert visibility across the platform.

• Improved handling of inactive Power BI reports in edge cases.

Highlights

Home Page: The home page now welcomes you to Datalogz' Control Tower and shows you a new Alerts widget, an overview of you connectors and their status and your teams' activity. Depending on your role (Root User, Admin, or Member), you'll see a home page designed for you.

What's New

• Entra ID Integration: We've introduced a new Entra ID tab in Settings. You can now connect to Entra ID to sync valuable metadata, including user identities, departments, and group memberships.

• Enhanced BI Similarity Insights: The BI Similarity tab is now available in preview to help you drill down into similar Power BI reports, dashboards, and datasets. This feature now clearly presents identified similar assets and their comparison details, helping you manage your BI landscape more effectively.

Key Improvements & Fixes

• "Contact Us" now conveniently opens your default email client with pre-filled subject and description.

• New Power BI workspaces are now synced with existing connectors after each refresh.

• Connector re-authentication scenarios have been improved; connectors now work seamlessly after re-authentication.

Inventory is your operational catalog of every BI asset across tools (Power BI, Tableau, Qlik Sense, Sigma, Spotfire, Databricks, and SharePoint). Built from platform metadata and usage logs, it is the door to governance, cost control, and migrations of your BI estate.

Inventory opens on two tabs. Summary is where you start: estate-level health and usage ratios, what was created or updated in the last 30 days, your most-viewed reports, and your favorites, enough to tell you where to spend the day. Assets is the full searchable grid, with the columns, filters, and views you need to turn any of those signals into a worklist.

Inventory views:

• Team Inventory that shows all assets within a defined team boundary (its projects, streams, or workspaces), with ownership and health in context.

• Global Inventory that has a cross-platform search and filtering across all connected BI tools, so you can discover, compare, and act on assets across the entire estate.

• Change detection: the "Start here" panel shows what was created and updated in the last 30 days, with field-level detail on datasets, so the renamed column that silently breaks a downstream report surfaces in days instead of weeks.

• : workspaces/projects/streams, folders, reports & dashboards, datasets/extracts, data sources, KPIs, and more.

• Operational state: staleness, failed refreshes, orphaned assets, and similarity alerts, each linked to the asset with quick actions to resolve.

• Users & ownership: stable IDs, licenses, owners, and teams.

Highlights

Get deeper insights into your Power BI environment with our newly introduced BI Similarity tool!

• Our BI similarity tool has been inproved to include more parameters for report and dataset comparison. This means more efficient management and identification of redundancies or inconsistencies.

• We've made improvements to the BI Similarity interface, making it easier to visualize and interact with your report similarities.

Key Bug Fixes:

• The "Users" section within your Power BI Inventory Table is now correctly populating, providing you with a complete view of your Power BI users.

• You can now reliably update your connectors from the connector details page without encountering errors.

BI 360 is the executive view of your entire analytics estate. It brings adoption, usage, licensing, cost efficiency, trends, and a global inventory together in one decision-ready dashboard, across every connected BI tool.

BI 360 answers one core question: how healthy, valuable, and cost effective is your BI ecosystem, right now and over time?

• : an auto-generated daily narrative of BI health, changes, and signals, ready to share with leadership.

• : asset counts and health per layer (organizational, reporting, data, and user) for every BI tool, with department breakdowns when a user directory is connected.

An alert is the direct result or notification that is triggered when a 's condition is met. It's the action that the system takes to inform you that something requires your attention. It's designed to be actionable, providing you with the necessary information to diagnose and resolve an issue.

Examples:

• "The 'Monthly Revenue' dataset refresh failed at 2:00 AM." (This is the alert triggered by a monitor on dataset refresh status.)

• "A new report was created in the 'Finance' workspace by a user with a non-finance role." (An alert from a governance monitor.)

• "The 'Executive Dashboard' has not been viewed in over 90 days." (An alert from a monitor on report usage.)

We recommend the following best practices:

• Always check lineage before deleting assets

• Start investigations from Inventory → Asset → Lineage

• Use health tags + lineage together for prioritization

• Focus on assets with:

Analytics ops teams who already run Control Tower can now get their answers without interacting with the web interface.

The data is already there. What may not be that obvious in the UI is how to reach it: open the app, pick the connector, filter the Inventory table, export, reconcile, paste into the doc you were writing. The Control Tower MCP server simplifies this. You ask in the window you are already working in, and the governed answer comes back with the assets behind it.

Release date: May 20th, 2025

The 2.5.0 Release of Datalogz focuses on advancing the actionability of alerts and improving Monitor Summary Page layout. This release also includes foundational improvements in testing, observability which will further be enhanced in the upcoming versions.

• Introduced monitor actions for Power BI (e.g., delete, export, update refresh schedule, take ownership) with corresponding scripts and UI support.

• Added new monitor for detecting duplicate Power BI dataset measures.

• Enhanced alert management with bulk workflow updates, sorting, and consolidated alert statistics by status.

• Updated monitor classifications and action associations for Power BI, Qlik, and Tableau to improve governance, performance, and security coverage.

• Refined alert filtering, sorting, and statistics, including exclusion of resolved/done alerts from counts.

Monitors Summary Page Enhancement:

Future releases will add:

• Automatic triggers: run a workflow when an alert opens, closes, or changes status without any manual action.

• Scheduled triggers: run a workflow on a recurring cron schedule.

• Additional , including ServiceNow ticket creation and approval gates.

Workflows turn a monitor alert into a one-click action. Instead of manually deciding what to do each time an alert fires, you configure a workflow once and it appears as a button on every matching alert, ready for anyone with access to run it.

Each workflow runs one or more , which are the individual actions the workflow takes (for example, sending a notification email). In this release, workflows are triggered manually from monitor alerts, and the available plugin is .

Notification workflows sit on top of:

• Inventory: where assets, ownership, and health are defined

• Monitors & Alerts: where issues are detected (unused, orphaned, failed refresh, etc.)

They act as the execution layer that ensures these signals lead to action.

BI Similarity automatically detects and quantifies duplication across your BI estate: the multiple versions of the same report or dataset that different teams built and never reconciled. It finds duplicate and near-duplicate assets in Power BI and Tableau, scores how similar they are, and gives you the tools to act.

With BI Similarity, you can use the Cluster Map to:

• through similar reports and datasets.

• what makes the assets similar. Open any pair to see a side-by-side Comparison view with the similarity score, the signals driving it (e.g., overlapping data source), and a metadata diff that highlights which fields are the same and which differ

• New Inventory landing page with instant counts for assets, alerts and similarities.

• Side panel on every asset with health, owners, and open alerts.

• Unified search with richer attributes and filters.

• CSV export (up to 500 rows)

Filters turn the Inventory from a list into answers. This guide works through one common use case end to end; the same pattern applies to most cleanup and governance questions.

Surface newly created Power BI reports in production that are unhealthy, excluding test artifacts, so they can be fixed before they impact business users.

Why it matters. New reports have had less time for validation, which makes early-life issues more likely: configuration gaps, performance inefficiencies, or incomplete modelling. Left unnoticed, unhealthy production reports degrade the user experience, increase refresh and capacity pressure, create downstream reliability issues, and reduce trust in production reporting. Reviewing them regularly lets your team intervene early.

Who owns it. Typically BI administrators, analytics platform owners, and data governance or Center of Excellence teams: the roles responsible for production health and standards.

Steps:

1. Open Control Tower and navigate to the team that contains your production Power BI workspaces.

Release date: October 1st, 2024

What's New

Enhanced Insights Page

• BI Tool-Specific Insights: The Insights page has been enhanced to provide customized visualizations based on the type of BI tool being used. Whether you're using PowerBI, Tableau, or Qlik, the Insights page now adapts to show tailored metrics and trends specific to each tool, helping users better understand their BI environments in the context of the tools they rely on.

Enhanced Default Monitors

• More Comprehensive Default Monitors: We’ve upgraded our Default Monitors to be more robust and comprehensive, addressing a broader range of issues under the four pillars of Security Monitoring, BI Governance, Platform Administration, and Capacity Monitoring. These enhanced monitors provide deeper insights into your BI environment, identifying more potential issues and improving the overall monitoring experience.

New Default Monitor Features

• Show/Hide Monitors: Users can now choose to show or hide specific monitors, allowing for a more personalized and clutter-free view of their monitoring dashboard.

• Clone Monitors: You can now clone default monitors, making it easy to create custom monitors based on existing configurations.

• Detailed Monitor Data: Access richer, more detailed data in each monitor. View query logic, underlying metadata, and track changes over time to gain more granular control over your BI monitoring.

Custom Monitors

• Create Custom Monitors by Duplicating Default Monitors: Users now have the ability to create custom monitors by duplicating Default Monitors and editing their SQL queries to tailor the monitor to specific needs. These custom monitors can be deleted or further modified, providing full flexibility in how you monitor your BI environment.

• My Monitors vs Default Monitors: To keep things organized, we’ve introduced two folders in the Monitor section: My Monitors and Default Monitors. The Default Monitors folder houses the pre-built monitors created by our team, while the My Monitors folder holds user-created monitors, giving you a clear separation between system and custom configurations.

Enhanced Alerts Table

• Improved Filtering, Search, and Column Data: We’ve enhanced the Alerts Table to make managing and resolving alerts even more efficient. Users can now apply more granular filters, perform faster searches, and access more detailed column data to quickly identify and address critical issues.

Launch of Teams

• Teams Feature: We’ve introduced Teams functionality! Organizations can now create and manage teams within the platform. Teams allow users to collaborate more effectively by organizing groups with shared BI goals and content. Assign BI connectors, workspaces, and assets to specific teams, improving collaboration, accountability, and management across departments.

Want to go deeper on BI Similarity? These resources cover both the why and the engine behind it:

• https://resources.datalogz.io/solving-bi-similarity-with-datalogz-anouk-gorris/

• https://resources.datalogz.io/inside-the-datalogz-bi-similarity-engine-pablo-lerdo-de-tejada/

Overview

The BI Similarity Cluster Map helps you quickly find similar BI assets. It's an interactive map that groups similar reports and datasets together, letting you use filters to easily explore and pinpoint the exact clusters you're looking for.

How to find clusters of similar assets

1. Go to your preferred team.

2. Click on the BI Similarity tab.

3. Click on the type of asset you are interested in. You can choose between the following asset types:

   • Power BI Semantic Models

   • Power BI Reports

   • Tableau Data Sources

   • Tableau Dashboards

4. Review the asset clusters.

The graph shows all available similar asset clusters through edges and nodes.

Each node represents an asset (report or dataset). The color of the node represents the location of the asset, for example a Power BI workspace or a Tableau project. Selecting a node marks the node with a dotted line. Nodes outside of the selected cluster are blurred.

Each edge represents a relationship between two similar assets. The edge also has a similarity score and a state.

A toolbar at the bottom of the cluster map controls how the graph is displayed:

• Labels: Show or hide the asset names on the nodes.

• Score: Show or hide the similarity scores on the connections between nodes.

• Legend: Show or hide the legend. Use the dropdown next to it to pick the property that colors the nodes, such as workspaces.

• Top Views %: Narrow the map to the most viewed assets. Lower the percentage to focus on the assets users actually open.

Use the + and - buttons to zoom in and out, the arrow controls to pan across the map, and the center button to reset the view.

The graph initially shows all similar asset clusters. When dealing with a large volume of assets, simply use the filters to refine your view and quickly pinpoint what you're looking for. The filters will change depending on the asset type that you have selected in the previous step.

The following filters are available:

The core building blocks you will see everywhere in Datalogz Control Tower.

Assets

An asset is any resource in your BI environment: reports, dashboards, datasets and semantic models, dataflows, workbooks, apps, and more. Control Tower keeps a unified inventory of every asset across all your connected BI platforms, enriched with ownership, usage, lineage, and health information.

What you do: browse the inventory to see what exists, who owns it, and how it is used. Star the assets you care about, save filtered views for your team, and export lists when you need them.

Platform Context

Every BI tool organizes content differently: Power BI uses workspaces, Tableau uses projects, Qlik Sense uses streams. Platform Context is the single term Control Tower uses for all of these, so you can work consistently across tools without translating each platform's vocabulary.

Connectors

A connector links Control Tower to one of your BI platforms, such as Power BI, Tableau, or Qlik Sense. Using credentials you provide, it reads metadata from that platform on a schedule, so your inventory, monitors, and alerts stay current.

What you do: an admin sets up each connector once and keeps credentials current. Syncing happens automatically from there. Read more in Datalogz Security.

Monitors

A monitor is a continuous check on your BI environment. Each monitor watches for a specific condition, such as a stale dataset, an unused report, or an unusual access pattern, and is tagged with the pillar it protects and a recommended fix. Default monitors are curated by Datalogz and work out of the box. My Monitors are your own: duplicate a default monitor and tailor its criteria to your organization's needs.

What you do: enable the monitors you need from the Monitor Catalog, set who gets notified, and adjust schedules if needed.

An alert is created when an asset breaches a monitor's rule. Each alert tells you the affected asset, what went wrong, who owns it, and what to do about it. Alerts have a status (to do, in progress, resolved) and a priority, and every change is recorded in an audit trail.

What you do: triage alerts from the Alerts page: assign them to team members, set priority, comment, and resolve. Bulk actions let you handle many alerts at once, and alerts close automatically when the underlying issue no longer exists.

A team groups people who work with the same BI content, typically by department or function. Teams scope which connectors, views, and alerts members see, so everyone works on the content they are responsible for.

What you do: organize users into teams so access stays clean and alerts route to the people who own the affected content.

The Home dashboard is your team's daily starting point. It summarizes alerts by pillar, priority, and status, with a view of everything or just the items assigned to you.

What you do: check Home to see what needs attention today and jump straight into triage.

BI360 is the executive view of your entire analytics estate: inventory growth, adoption and engagement, license utilization, department health, and trends over time, across all connected BI tools.

What you do: use BI360 to track the health of your analytics estate over time and report progress to leadership.

Dependency Lineage helps you:

• Understand how assets are connected

• Analyze impact before making changes

• Identify cleanup opportunities

• Improve governance and trust

It turns Inventory from a static catalog into a dynamic system of relationships. Here is how you interpret the lineage view.

These are the inputs to your asset.

Examples:

• Semantic models powering a report

• Dataflows feeding a dataset

• Source systems behind a model

If empty: “No upstream assets found” means the asset is either:

• A top-level source

• Or lineage is not available from the BI tool

These are the outputs that depend on your asset.

Examples:

• Reports built on a semantic model

• Dashboards using reports

• Other models or derived assets

This section is shown as a table with rich metadata, including:

• Asset name & type

• Owner

• Last modifier

• Health status (e.g., Stale, Unused)

The Actions section allows you to easily:

• Learn more about the dependency in the Control Tower Lineage

• Go to the asset in its source tool, like Power BI or Tableau

• The number next to each section shows how many assets are connected

• Helps quickly assess impact size

You’ll see tags like:

• Unused

• Stale

These come from and help you understand:

• Whether dependencies are still relevant

• Where cleanup opportunities exist

Each downstream asset includes:

• Owner

• Last modifier

Use this to:

• Contact stakeholders

• Validate whether something can be changed or removed

This release delivers a rebuilt Tableau connector with full multi-host and multi-site support, expanded asset mapping workflows in User Directory for Power BI and Tableau, and significant improvements to BI360 department-level reporting. This release also broadens Power BI inventory with capacity, domain, gateway, and usage analytics, extends Sigma with lineage, and includes performance improvements across alerts, monitoring, and BI Similarity.

What's New

• Tableau Multi-Site Support: You can now connect multiple Tableau hosts and sites within a single connector setup. Site discovery, per-site authentication, and per-site management are all handled from one place and if a sync partially fails, you'll see exactly which site had the issue and where it came from.

• Asset Mapping for Power BI and Tableau: Administrators can now upload a mapping file to associate Power BI and Tableau assets with departments or custom groups. Once uploaded, Datalogz handles the sync automatically, and you can track status, re-sync on demand, or update the file at any time.

• BI360 Department Health: BI360 now shows health snapshots for each department, including which are most active and which are at risk. You can drill into department ownership across all your BI tools, including Tableau, and see adoption broken down by connector.

• Power BI Capacities: A new Capacities tab in Power BI inventory shows how workspaces, reports, and semantic models are distributed across your capacity. Datasource cards now include connection details and gateway health so you can quickly spot configuration issues.

• Sigma Lineage: Lineage is now available for Sigma, covering workbooks, reports, and data models, including connections back to underlying data sources.

• Tableau Inventory: Tableau assets now show host, site, and owner information, making it easier to understand where assets live in large multi-site environments. Dashboards, worksheets, and stories appear as distinct asset types, and team scoping can now filter by host and site.

• BI360: The global inventory now includes Pillars, and Cost Management links have been updated to reflect pillar-based alerting. BI360 views are better scoped to the connectors your organization actually uses.

• Power BI Domains and Usage: Workspace domain information is now surfaced in inventory with filtering support. Report usage analytics are available so you can see which reports are being used and by whom.

• Alert and monitor breakdowns load faster thanks to smarter caching. Caches update automatically when you change monitor settings or workflows, so you're always seeing current data.

• BI Similarity graphs render more reliably and cancel cleanly when navigating away.

• Fixed a Power BI issue with domain parsing that affected workspace filtering.

• Fixed pagination in Sigma workspace and member lists.

The Dependency Lineage in Inventory shows how BI assets are connected.

It answers:

• What does this asset depend on? (upstream)

• What depends on this asset? (downstream)

This gives you a complete view of data flow, from source → model → report → dashboard.

Why Dependency Lineage Matters

Without lineage:

• You can’t see impact before making changes

• Broken reports are hard to trace

• Cleanup is risky

With lineage, you can:

• Understand BI dependencies instantly

• Identify high-impact assets

• Safely modify or delete content

• Detect redundant or unused chains

Lineage is foundational for governance and cleanup.

1. Open Inventory

2. Select any asset (report, dashboard, semantic model)

3. Navigate to the Lineage tab

The Datalogz MCP servers allow you to ask your AI assistant a question about your analytics estate and get the governed answer back in plain language, without anyone opening the app.

Datalogz Control Tower already knows what exists across every connected platform: which assets are there, who owns them, what is used, what is duplicated, what is failing, and what breaks if you change it. The Control Tower MCP server exposes that same picture as a set of tools any Model Context Protocol client can call. Ask "which Power BI reports has nobody opened in 90 days?" or "who can reach the Finance workspace?" and your assistant queries Control Tower directly, then answers from the result.

Availability

• Available in production:

  • MCP Server for Analytics Ops teams (Claude)

  • MCP Server for (Copilot)

  • MCP Server for Databricks Genie (One and Code)

• Available in preview:

  • MCP Server for Business Users (Claude)

  • MCP Server for Business Users (Copilot)

The MCP server is a read path over the same warehouse the app reads. Numbers reconcile with BI360, Inventory and Alerts, and are as fresh as your last connector scan. The server adds no lag of its own, and does no scanning itself.

Most responses include a detail_url pointing at the asset in app.datalogz.io, so an answer in chat stays one click from the full asset page. When you want to act on what you found, whether that is assigning the alert, notifying the owner or running the workflow, you do it in the app.

Next steps

• Review

Concept details opens as a side panel from the scorecard, from a search, or from a direct link on the Metric Explorer tab. The header shows the concept name, its status, and how many departments, definitions and data models it spans.

The panel has two views: Definitions and Lineage.

Definitions

The Reference definition card is shown first: its department, metric name, expression, a Certified tag if its semantic model is endorsed, and a link to the data model with its report count.

Every other metric in the concept follows as a card with:

• the department and metric name

• its label (Identical, Equivalent, Divergent or Conflicting)

• how structurally similar it is to the source definition, as a percentage

• its expression, with the lines that differ from the source definition highlighted

• a link to its data model in Inventory, and the number of reports that use it

Metrics that share the same definition are grouped together.

To compare a definition with the source definition:

1. Click Show expanded expression to see the expression with every referenced metric written out in full. Two metrics that look different on the surface often turn out to call the same base metrics, and the reverse happens too.

2. Click Compare with source to open a side-by-side diff of the expanded source definition and the selected metric.

3. Click the data model name to open the semantic model in Inventory and find its owner.

Use Sort metrics by to order the cards by Structural similarity (least similar first), Department or Workspace. Large concepts load in pages; click Load more metrics to see the rest.

The Lineage view draws the concept as a graph: the data model and table each definition lives in, the metric itself, and the reports, visuals and dashboards that use it. Other definitions of the concept appear as dashed nodes, colored by status, so you can see which branch of the estate runs on a different version of the metric. Click a data model or report to open it in Inventory, or a metric to open it in the Metrics Catalog.

Click Why this answer? to see how the concept was formed. The formation audit lists every candidate definition Control Tower considered, ranked by combined similarity, with the departments and metrics behind each one. A dashed line marks the membership threshold: candidates above it joined the concept, and candidates below it are shown struck through with the reason they were left out.

This is useful when a metric you expected is missing from a concept, or when a concept contains something you did not expect.

Department insights slice BI 360 by team, function, or business unit (for example Marketing, Finance, Sales, or R&D), so you see adoption, license use, and content ownership per department instead of only tenant-wide.

Once department data is connected, BI 360 adds:

• Department User Breakdown: adoption and activity per team.

• License Utilization by Department: allocated vs. active licenses per team.

• Department Dashboard Ownership: content ownership and inactivity per team.

• Department BI Health Snapshot: top active and at-risk departments on the Executive Summary.

Datalogz joins the department field on each user account in Entra ID to the users, owners, and licenses it ingests from your BI tools.

1. Confirm Entra ID is configured for your tenant.

2. Go to Settings > User Directory.

3. Set up the Entra ID connector (see the Entra ID guide).

4. Department dimensions appear in BI 360 within one ingestion cycle.

1. Go to Settings > User Directory.

2. Choose which tools (Power BI or Tableau) you want to map assets to departments for.

3. Create a CSV or Excel file with the columns asset_name, asset_id, and department. You can rename department to the language you use, for example Business Units.

4. Upload the file on the Asset Mapping card and click Sync.

The Summary tab is where you start in Inventory. An estate with thousands of assets and hundreds of open findings does not tell you what to do first. Summary does, by narrowing the whole estate to four questions you can act on today: how healthy is it, what changed, what do people actually use, and what am I watching.

Everything on the page is a jump-off point. Each tile, count, and asset links through to the filtered Assets grid or straight to an asset page.

What Summary shows

• Estate health at a glance. Ratio tiles for asset health and activity, each showing a healthy/unhealthy or active/inactive split with counts, scoped to the connector and team selected in the left nav.

• Change detection. The Start here panel lists what was created and updated in the last 30 days, with field-level detail on datasets: which tables, columns, and measures were added or modified, by whom, and when. This is where a renamed column surfaces in days rather than after it has quietly broken a downstream report for three weeks.

• Orientation shortcuts. Top Reports ranks your most-viewed reports with viewer counts, and Favorite Assets groups your starred assets by type. Both carry Asset Health badges, so you can see immediately whether the things people rely on most are in good shape.

Power BI example:

Databricks example:

Improvements

Expanded monitors across BI platforms

• Tableau: Governance, Performance, and Cost monitors to track drift, load times, and spend.

• Power BI: New Performance monitors to pinpoint slow workspaces and reports.

• Qlik: Cost, Performance, and Security monitors for end-to-end oversight.

BI Similarity upgrades

• Improved comparison scoring for more accurate “look-alike” detection.

• Additional Power BI metadata capture to enrich similarity analysis.

• Breadcrumbs added across pages for better orientation (no redundant “Home”).

• Consistent iconography via shared components.

• Guardrails to prevent duplicate team and connector names.

• Home page APIs: faster load and more stable summaries.

• BI Similarity: reduced compute time and smoother navigation.

• Inventory: noticeable speed-ups on large estates.

• Fixed rare 404 on Insights when no executive teams are set up.

• Corrected BI Similarity acceptance and upstream lineage edge cases.

• Fixed layout issues when cloning monitors.

Semantic Intelligence finds every definition of a business metric across your analytics estate, groups the ones that describe the same idea into a business concept, and shows where those definitions agree and where they have started to drift or even conflict.

Most organizations do not have a maintained business glossary. The real definitions of Revenue, Customer or Headcount live inside measures and metric views, copied and adjusted by every team that needed them. Semantic Intelligence reads those metrics as they are, so there is no ontology or glossary to author before you start. It works bottom-up from what your teams already built.

What's inside

• Metric Explorer: an estate-level view with key figures and a standardization scorecard, one row per business concept. Concept details: every definition of one concept side by side, compared against its source definition, with a lineage view down to the reports that use it.

• Metrics Catalog: every metric that was analyzed, searchable and filterable, with its expression and the concept it belongs to.

• Exclusions: control which semantic models are left out of the analysis, for example test or personal copies.

The Global Inventory is the single list of every BI asset across all your connected tools: reports, dashboards, datasets, models, apps, and folders, no matter where they were created. For each asset you see where it lives, who owns it, and whether it is healthy.

What you use it for:

• Eliminate blind spots across BI tools.

• Identify unused, stale, or orphaned assets.

• Improve governance, ownership, and accountability.

• Support cost and license optimization.

• Build a trusted foundation for cleanup and optimization initiatives.

The Metrics Catalog lists every metric Semantic Intelligence analyzed for the selected connector and team.

Click a row to open the metric's detail panel, with its type, department, data model, table, business concept, the expression as written and the expanded expression.

You can also reach Semantic Intelligence from : on a semantic model or similar asset page, the Data Attributes tab has an Open in Semantic Intelligence link.

Datalogz connects to BI tools exclusively via their authenticated REST APIs, ensuring secure and controlled access. The key points are:

• Read-Only Metadata Access: We only retrieve metadata—such as report configurations, usage statistics, and asset lineage—without accessing any underlying report data or user content. This guarantees data privacy and limits access scope.

• Authenticated API Calls: All API requests use credentials provisioned and managed securely through service principals or managed identities, ensuring only authorized access to metadata endpoints.

• Encryption in Transit: All communication between Datalogz and BI tools occurs over secure HTTPS connections, protecting metadata from interception or tampering during transmission.

• Metadata Storage Location: All metadata collected from BI tools is securely stored within a dedicated Datalogz AWS account to ensure isolation and control.

Release date: October 14, 2026

This release is about going deeper on every platform you connect. Databricks gains a Users tab, workspace access and lineage, BI Similarity now covers Sigma workbooks and data models, and Power BI dataflows appear in lineage. Semantic Intelligence also reaches the MCP server, so AI agents can ask what a measure means and who computes it differently.

This release helps your teams to:

• See who can reach each Databricks workspace and how data moves through Unity Catalog

• Find rebuilt Sigma workbooks and data models next to the rest of their duplicates

Release date: December 2, 2024

This release emphasizes connector improvements and Power BI refactoring, targeting enhanced functionality and performance, particularly for PBI. These platform enhancements align with our strategic goals to improve connector management, boost user engagement through superior UX, fortify system security, and ensure scalable technical performance.

• Streamlined Connector Setup and Management:

  • Connecotrs now have more detailed informationabout credentials, connection status, and authentication methods used for each data source. This provides better visibility and troubleshooting capabilities for administrators.

Asset Health is a status applied to each asset - Healthy, Unhealthy, or N/A - so teams can quickly triage issues, prioritize fixes, and confidently use or share trusted content. Health is determined by active, (e.g., refresh failures, staleness, orphaned ownership, similarity matches).

• Healthy: No active alerts, and relevant monitors are running for this asset type.

• Unhealthy: One or more active alerts and/or confirmed similarity/duplicate matches.

• N/A (No label): Monitors governing this asset type are turned off in the Monitor Catalog, so health can’t be assessed.

Datalogz' Control Tower provides the essential tools for a thorough comparison of similar assets. Once you see the overlaps, you can make informed decisions about their future. For example:

• If both assets serve a unique purpose, simply Accept their similarity.

• If it's safe to deprecate one of the assets, choose the best version and archive the redundant one.

• If both assets are similar, but can be consolidated, merge both assets to create a single, unified source.

The dedicated comparison interface facilitates informed decision-making and streamlines stakeholder outreach for efficient resolution.

Each workflow has a history view listing every session that has been run, including when it ran, who triggered it, and the outcome of each step. Access this from Settings → Workflows → Definitions, then open the workflow.

My Monitors are user-created monitors. Currently, users can only create new monitors by duplicating an existing Default Monitor and modifying it according to their needs. My Monitors provide users the flexibility to adjust the monitoring criteria, such as SQL queries and thresholds, to fit their specific requirements.

• Duplicating Default Monitors: Users can create My Monitors by duplicating an existing Default Monitor. This duplication feature allows users to build upon the existing structure of the default SQL queries and modify them according to their specific needs.

• Customizable Queries: Once duplicated, users can modify the SQL query, thresholds, and alert criteria of the monitor. This enables users to tailor the monitor to focus on specific assets, custom data conditions, or unique business requirements that are not covered by the default configuration.