Skip to content

Metadata impact report

Source code

The metadata impact report package calculates various metrics about your data landscape from the metadata you manage in Atlan.

Use cases

  • Monitoring the rollout of Atlan over time, or as your data landscape evolves
  • Identifying opportunities for cost savings, based on indicators in the metadata (such as assets that are unused)
  • Tracking adoption and enrichment of assets in Atlan, possibly as part of a gamification drive during onboarding or rollout sprints



The report will always produce an Excel file, but you can choose whether to also create a glossary of metrics in Atlan:

  • Generate glossary?

    Creates (or updates, if it already exists) a glossary describing the various metrics the report calculates. The numeric quantity for each metric is also updated each time the report runs.

    • Glossary name: name of the glossary in which to store the metadata metrics.

    Only creates the Excel output

  • Include details: whether to include detailed results (Yes), or only the overall quantified metrics (No) in the Excel file produced.


  • Email address(es): (optional) enter a list of email addresses, comma-separated, where you want the report to be sent as an attachment. The report will always be downloadable from the workflow run as well.

What it does

The package tracks the metadata metrics in Atlan, through a dedicated glossary, and also produces an Excel file report that consolidates all of the information into an easy-to-share file format.


A single glossary named as-specified in the input will be created (or updated, if it already exists).


One term will be created (or updated, if it already exists) for each of the metrics defined in the report. Each term will be complete with:

  • Name and acronym
  • Description of what it represents
  • A quantified number
  • A certificate indicating whether there are any caveats (draft) or not (verified)
  • A warning announcement describing any caveats with the metric
  • An information announcement describing any other points of note with the metric
  • Categorization of each term to represent is typical use

For details of each metric, refer to the glossary

For details about each metric, we recommend running the report in your Atlan environment and reviewing the metrics in the glossary it produces. There you can also capture any further information you like specific to your own needs and use of the metric: either by updating the description1 or providing even more details in a README.

Excel file

In addition to the terms, an Excel file will be produced that includes these sheets:



Acronym and name of the metric.


An explanation of what the metric measures, and how it can be used.


Quantified number for the metric, produced from the metadata in your Atlan environment.


An explanation of any of the caveats to be aware of with the quantified number.


Any other notes to be aware of regarding the metric.

Per-metric worksheet

If requested (using "include details"), a separate worksheet listing every asset that was counted as part of calculating each quantified metric is also included in the Excel report. The columns vary depending on the metric, but will typically include:


Type of connector for the asset, for example Snowflake.


Name of the database for the asset.


Name of the schema for the asset.


Name of the asset.


Type of the asset, for example table vs view.

Size (GB)

Amount of storage, in gigabytes, used by the asset (at source).


Approximate compute cost associated with queries run against the asset.


A link directly to this asset's detailed profile within Atlan.

How it works

The report is very modular, with each metric defined individually as:

  • A name, acronym, description, and any possible caveats or notes
  • A query that counts the assets that match a metric
  • A tabular heading and per-record format for listing out the detailed assets that fit the metric

The report itself simply iterates through each of these metrics and:

  1. Runs the query.
  2. Retrieves a total quantity from the result, to use as the overall quantified number.
  3. Iterates through the individual results of the search to output each detailed asset (if requested).

The glossary (for all) and term (for each metric) are idempotently created or updated at each step of the process with the details calculated.

  1. If you update the description through the UI, your own description will always take precedence. Even re-running the package will only ever update the background description, which will not appear on the UI and will not clobber or replace your overridden description.