Sigma Integration Discovered Resources
Overview
The Sigma integration discovers the following resources:
Sigma Account
Sigma Folder (Workspaces and Folders)
Sigma Data Model
Sigma Workbook
Sigma Element
Data Warehouse Tables (referenced by workbooks)
Sigma Account
A single resource of type sigma_account is observed for each configured Sigma integration, representing the top-level Sigma organization.
Properties
name
The organization name extracted from workbook URLs
type
always sigma_account
subtype
always sigma_account
native_id
The Sigma organization ID
external_links
Link to the Sigma application
Sigma Folders and workspaces
Folders and workspaces are organizational containers in Sigma. Workspaces are top-level folders, while folders can be nested within workspaces or other folders.
Properties
name
The folder or workspace name
type
always sigma_folder
subtype
sigma_folder or sigma_workspace
native_id
The unique folder/workspace ID in Sigma
created_at
The timestamp when the folder was created
updated_at
The timestamp when the folder was last modified
created_by
The email address of the user who created the folder
updated_by
The email address of the user who last updated the folder
owner
The owner of the folder
Sigma Data Model
Data models are reusable semantic layers in Sigma that provide business-friendly views of data warehouse tables.
Properties
name
The data model name
type
always sigma_data_model
subtype
always sigma_data_model
native_id
The unique data model ID in Sigma
created_at
The timestamp when the data model was created
updated_at
The timestamp when the data model was last modified
created_by
The email address of the user who created the data model
updated_by
The email address of the user who last updated the data model
owner
The owner of the data model
tags
List of version tag names associated with the data model
external_links
Link to open the data model in Sigma
Sigma Workbook
Workbooks are analytics documents in Sigma containing visualizations, tables, and analyses.
Properties
name
The workbook name
type
always sigma_workbook
subtype
always sigma_workbook
native_id
The unique workbook ID in Sigma
description
The workbook description, if provided
created_at
The timestamp when the workbook was created
updated_at
The timestamp when the workbook was last modified
created_by
The email address of the user who created the workbook
updated_by
The email address of the user who last updated the workbook
owner
The owner of the workbook
tags
List of version tag names associated with the workbook
total_read_queries_14/30/60d
When integrated with a supported warehouse, the total read queries for the timeframe are propagated to the resource.
total_read_cost_14/30/60d
When integrated with Snowflake warehouse, the total read cost for the timeframe propagated to the resource.
total_read_credits_14/30/60d
When integrated with Snowflake, the total read credits for the timeframe propagated to the resource.
Sigma Element
Elements are individual components within a Sigma workbook, such as tables, visualizations, or calculations. Each element may contain SQL queries and can reference other elements or data warehouse tables.
Properties
name
The element name
type
always sigma_element
subtype
always sigma_element
native_id
The element ID in the format {workbook_uri}/{element_id}
Data Warehouse Tables
When a Sigma workbook references a data warehouse table, Euno automatically observes that table if it hasn't been discovered yet.
Properties
name
The table name
type
always table
subtype
always table
database_technology
The data warehouse type
database
The database name
schema
The schema name
Relationships
Container Relationships
Sigma Account → Workspaces: Workspaces are top-level folders under the account
Workspaces → Folders: Folders can be nested within workspaces
Folders → Subfolders: Folders can contain other folders
Folders → Workbooks: Workbooks belong to folders
Sigma Account → Data Models: Data models are direct children of the account
Workbooks → Elements: Elements belong to workbooks
Lineage Relationships
Workbooks → Elements: Workbooks have their
upstreamset to their elementsElements → Tables: Root elements (elements that directly reference a data warehouse table) has
upstreamset to the data warehouse tablesElements → Elements: Non-root (elements that only reference other elements in the workbook) has
upstreamset to the elements they referenceElements → Data Models: Elements that reference data models have the data models they reference added to their
upstream
Column level lineage
Elements -> Table Columns: Root elements has
upstream_fieldsset to the columns they reference in the upstream data warehouse tables
Last updated