There are several built-in options for coloring graph nodes to give you more information about your pipeline:
| Coloring option | Description |
|---|---|
| No color | Would remove coloring altogether |
| Custom color | Allows you to select nodes and assign them a color by clicking on the Color button |
| Data Catalog | Nodes would be colored based on the Data Catalog collection they are in. If the node belongs to more than one collection it would be colored as “In multiple collections“ |
| Folder | Colors the nodes by name of the folder the resource is located in |
| Issues | Colors the nodes by the number of Foundry issues assigned to them. This option would also allow you to filter by issues labels. |
| Permissions | Colors the nodes by the level of access the user has to the data or the resource. If you have access to the resources on the graph, this view also allows you to choose any Foundry user and view their permissions. |
| Project | Colors the nodes based on the Foundry Project they are in. |
| Repository | Colors the nodes based on the code repository used to create them. You can either color the nodes by the name of the repository, or by its type (e.g. Code Repository, Code Workbook). |
| Resource overview | This view colors the node by details of the resource. The details of the resource generally refer to the way the resource was created (such as in Contour, Code Workbook, Fusion spreadsheet sync, by Upload, etc.). |
| Build status | Indicates the current build status of each dataset on the graph. If the nodes are grouped the more severe status would be presented. |
| Data Heath | Indicates the status of resources health checks with the ability to filter to only watched health checks. If the nodes are grouped, the color of the group would indicate the most severe health chceck status of the group. |
| Out-of-date | This option would indicate if the data or logic is out of date relative to the dataset ancestors. Out-of-date with parent means a direct parent of the resource had been updated and the resource itself hasn't yet updated accordingly. Out-of-date with ancestor means the resource is up-to-date with its direct parents, but there is a resource upstream that is more updated. This options allows you to filter for two types of updates: Data and Logic. Data out-of-date means the data was updated in an ancestor and the resource hasn't yet picked up the update in a build. Logic out-of-date means job-specs has changed. |
| Schedule count | Indicates the amount of build schedules set on a dataset with the option to filter out paused schedules. |
| Sync status | If there are syncs set on the dataset, this option would indicate the status of the sync |
| Time last built | Indicates the time since the last time the dataset was successfully built. |
| Build duration | According to the most recent successful build of each resource, this option would indicate the approximate build duration |
| Files | Colors the nodes on the graph by files-related metrics: Average file size, count of files and dataset size |
| Row count | Colors nodes by the number of rows in each dataset. If row count does not exist, it could be calculated in the dataset details helper or in the dataset view in Foundry (dataset app). |
| Spark usage | Colors each node by Executor run/CPU time in a given period |
| User views | Colors nodes by the number of user views |
| Branch | Indicates the currently viewed branch of each node on the graph. |
| Code Status | Indicates the code status for this node/dataset. CI running means CI checks are currently running for this node. CI Failed means that CI checks failed on this node. Out of date means that the code is out of date for this node. Unavailable means that the node/dataset is not a stemma backend or that the user is lacking permissions. |
| Storage | Indicates where data is stored. Will be Foundry unless you are using Virtual Tables. |
| Compute [Experimental] | Indicates if a transformation ran using external compute. Will be Foundry for all customers until further rollout. |
| Transaction type | Indicates each nodes transaction type: Append or Snapshot |