🎉 What's new

Announcing an upgrade to the Microsoft Power BI connector, now supporting dataflows in lineage to show upstream lineage to sources.

Data teams often rely almost exclusively on dataflows to pull data from upstream sources such as Snowflake and Oracle to Power BI. This represents one of their sources of data and end-to-end pipelines today for analytics use cases. With this release, data teams will now be able to trace root cause or impact analysis efficiently through Atlan!

✨ Let's dig deeper

Here's what's in store for you:

• Power BI dataflows will be cataloged as assets.
• Power BI dataflows will be visible as process entities on the lineage graph.
• Nested dataflows will be visible as related assets.
• Power BI tables will be visible as related assets.
• Power BI data sources (connection assets) will be visible as related assets.
• If dataflows are used at source, Atlan will display dataflows in the lineage graph to connect Power BI tables to upstream sources.
• This is currently only supported for the following upstream sources — Microsoft SQL Server, Oracle, SAP HANA, and Snowflake.

👏 Give it a shot

Explore the new enhancements to the Microsoft Power BI connection in Atlan!

🎉 What's new

The Microsoft Power BI connector now supports multiple SQL connections for automated lineage!

Here's what's in store for you:

• While crawling Power BI assets in Atlan, you can now select one or more SQL connections from a list of connected sources in Atlan.
• This will enable upstream lineage from Power BI when your semantic models, reports, and dashboards are powered from multiple SQL sources.
• If you do not specify any existing connections, Atlan will default to considering all available connections for supported SQL sources to generate lineage.

🎉 What's new

Atlan now supports crawling metadata from multiple MongoDB clusters for the Azure Cosmos DB for MongoDB connector! If you have multiple clusters across different subscriptions within the same Azure account, Atlan will now be able to connect and crawl metadata from both RU- and vCore-based deployments.

✨ Let's dig deeper

You can set up the Cosmos DB connector to:

• Connect and crawl metadata from multiple clusters — Atlan now supports connecting to and crawling metadata from multiple MongoDB clusters.
  • For each of your vCore-based clusters, you will need to authenticate with a connection string. Atlan will not be able to automatically discover and catalog metadata from your vCore-based clusters. You will need to manually register or remove connection strings as you create or remove clusters at source.
  • For each of your RU-based clusters, Atlan supports service principal authentication, and requires you to assign the Cosmos DB Account Reader Role for each cluster to the service principal. As new RU-based clusters are added, they will automatically show up in Atlan. If removed, the cluster metadata will also be removed from Atlan.
• Crawl metadata from a mix of vCore- and RU-based clusters — if your Microsoft Azure Cosmos DB deployment includes a mix of vCore- and RU-based accounts, you can configure both to fetch metadata. You can then use the vCore and RU deployment option to crawl your Microsoft Azure Cosmos DB assets.
• Discover accounts — this newly supported asset type represents each cluster running across all subscriptions. This can help your group your databases by clusters. To view supported attributes, refer to our documentation. Note that most MongoDB cluster-level attributes are unavailable for vCore-based deployments. This is because these clusters do not support service principal authentication.

👏 Give it a shot

Ready to explore the revamped Cosmos DB connector? Integrate Cosmos DB and Atlan to explore more:

• How to set up Microsoft Azure Cosmos DB
• How to crawl Microsoft Azure Cosmos DB
• What does Atlan crawl from Microsoft Azure Cosmos DB?

🎉 What's new

Atlan now supports displaying groups for your Apache Airflow tasks on the pipeline graph. Task groups help you logically group tasks in Apache Airflow. This release provides additional context for your Apache Airflow assets in Atlan. Supported for all Apache Airflow distributions — Apache Airflow, Amazon MWAA, Astronomer, and Google Cloud Composer.

Additionally, clicking on an asset in the pipeline graph now updates the asset sidebar to give you all the context you need.

🎉 What's new

Atlan now supports additional upstream sources for Microsoft Power BI lineage — Oracle and SAP HANA!

✨ Let's dig deeper

Once you have set up Microsoft Power BI, here's what in store for you:

• Upstream lineage to Oracle tables and views — Atlan generates lineage for the following methods of Oracle connectivity: connection string and connect descriptor. Support for regular and native queries (custom SQL) is also available. Lineage generation for TNS Alias connectivity is currently not supported due to unavailability of database metadata. 
• Upstream lineage to SAP HANA tables, views, and calculation views — Atlan supports regular and native queries (custom SQL) for lineage generation.

👏 Give it a shot

Explore additional upstream sources for Microsoft Power BI lineage, and better understand data flows in your data estate. Learn more: What lineage does Atlan extract from Microsoft Power BI?

🎉 What's new

Atlan now supports cataloging alerts and incidents from Monte Carlo! To best reflect the status of your assets at source, Atlan will display alerts and incidents, wherever applicable. You can view alerts and incidents on assets in asset discovery, asset profile, and lineage graph. You'll also be able to track the count of incidents on an asset, explore them in detail from the asset profile, and so much more!

Learn more: What does Atlan crawl from Monte Carlo?

🎉 What's new

Announcing two small but mighty enhancements to improve your lineage experience in Atlan:

• You can now find specific columns on the lineage graph using the Column filter in the search menu.
• Partial assets are now visible in the asset sidebar when viewing the pipeline graph. Get more context on the inputs and outputs for your Apache Airflow tasks and Apache Spark jobs.

🎉 What's new

Following up on the recent release of dbt column-level lineage, announcing some improvements to your experience of dbt materialized asset lineage:

• View lineage for all materialized tables — previously, lineage was shown for any one of the dbt materialized tables and missing for other tables. In addition, for each dbt workflow run, it would keep switching between the different materialized tables. Atlan will now display lineage for all dbt materialized tables.
• Materialized lineage will be grouped by jobs — previously, materialized lineage was grouped at the environment level, resulting in a mix of assets from different environments. Say bye bye to that! Lineage for materialized tables will now be grouped by jobs.
• All materialized tables linked to a given model and source — better understand your dbt materialized asset lineage with materialized assets linked to dbt models and sources.
• Upstream lineage to dbt source tables — view dbt source tables in materialized lineage.

🎉 What's new

Atlan now supports Private Service Connect for the Google BigQuery connector! This enhancement offers improved security and reliability to all data teams.

Here's how this can help you:

• Enhanced security — private network link connectivity ensures secure data transfer by utilizing a dedicated, private connection.
• Compliance — meet regulatory and compliance requirements by ensuring data remains within a private network environment.

Learn more: How to crawl Google BigQuery

🎉 What's new

You can now leverage the power of Atlan AI to improve existing asset descriptions! Transform your asset descriptions into informative, consistent, and business-friendly documentation in just a few clicks. Save time, use Atlan AI to refine your current descriptions!

Learn more: How to use Atlan AI for documentation