Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.planasonix.com/llms.txt

Use this file to discover all available pages before exploring further.

Impact analysis predicts which pipelines, datasets, dashboards, and reverse ETL syncs depend on an object you plan to change. You reduce surprise outages by reviewing the dependency graph before merges, renames, or type changes.

​
Premium feature

Impact analysis is a Premium capability (bundled or add-on per your order form). If the tool is unavailable, you can still use catalog ownership notes and manual pipeline search, but you lose automated dependency graphs.

​
Dependency graphs

Enter a table, topic, column, or pipeline node; Planasonix renders upstream and downstream dependencies:
  • Ingestion jobs that populate the asset
  • Transforms that read or write it
  • BI extracts, notebooks, or semantic models linked via integrations
Graph depth controls how many hops you display—start shallow, expand when investigating cross-domain effects.
1

Select the change target

Pick the warehouse table or stream field you intend to modify.
2

Review downstream consumers

Note dashboards, syncs, and scheduled jobs in the highest business-criticality tiers first.
3

Coordinate owners

Notify teams with open PRs touching the same graph edges.
4

Plan migration

Ship additive changes first, dual-write if needed, then retire old fields with confirmed zero downstream references.

​
Change impact assessment

Renames and type changes rank as high risk; impact analysis lists parsers and SQL that reference old names.
Impact analysis reflects last-known metadata. If external systems consume data outside Planasonix, maintain a manual appendix for those dependencies.

Data contracts

Encode allowed changes with versions.

Observability dashboard

Watch for regressions after risky releases.