> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/business-intelligence/cube-core-integration/cube-core-integration-discovered-resources.md).

# Cube Core Integration Discovered Resources

## Overview

The Cube Core integration discovers the semantic models defined in your Cube schema YAML files. It discovers the following resources:

* Cube deployment (`cube_deployment`, when **Instance slug** is configured)
* Cube (`cube_cube`)
* Cube view (`cube_view`)
* Cube dimension (`cube_dimension`)
* Cube measure (`cube_measure`)

Cube URIs start with `cube.<instance_slug>`. When **Instance slug** is not set, cubes and views use the `default` URI namespace (`cube.default`) and do not have a `cube_deployment` parent.

## Resource hierarchy

```
Cube deployment (only when Instance slug is configured)
├── Cube
│   └── Cube dimension / Cube measure
└── Cube view
    └── Cube dimension / Cube measure
```

## Cube deployment (`cube_deployment`)

A single `cube_deployment` resource is observed when **Instance slug** is set on the source. It groups all cubes and views for that Cube instance.

| Property    | Type   | Description                                                             |
| ----------- | ------ | ----------------------------------------------------------------------- |
| `name`      | string | Instance display name, or the instance slug when no display name is set |
| `type`      | string | Always `cube_deployment`                                                |
| `native_id` | string | Configured instance slug                                                |

**URI pattern**

```
cube.<instance_slug>
```

Example: `cube.production`

## Cube (`cube_cube`)

Cubes are semantic models defined in Cube schema YAML. Each cube typically maps to a warehouse table through `sql_table`.

| Property                  | Type   | Description                                                           |
| ------------------------- | ------ | --------------------------------------------------------------------- |
| `name`                    | string | Cube title from schema, or cube name when no title is set             |
| `type`                    | string | Always `cube_cube`                                                    |
| `native_id`               | string | Cube name from schema                                                 |
| `description`             | string | Cube description when present in schema                               |
| `raw_code`                | string | YAML fragment for this cube                                           |
| `database_technology`     | string | Resolved warehouse technology                                         |
| `database_schema`         | string | Default schema used to qualify unqualified table names                |
| `no_compiled_code_reason` | string | Reason warehouse table lineage could not be resolved, when applicable |

**URI pattern**

```
cube.<instance_slug>.cube.<cube_name>
```

Example: `cube.production.cube.orders`

## Cube view (`cube_view`)

Views expose subsets or aliases of cube members to consumers. View-scoped dimensions and measures are emitted under the view, not the underlying cube.

| Property      | Type   | Description                                               |
| ------------- | ------ | --------------------------------------------------------- |
| `name`        | string | View title from schema, or view name when no title is set |
| `type`        | string | Always `cube_view`                                        |
| `native_id`   | string | View name from schema                                     |
| `description` | string | View description when present in schema                   |
| `raw_code`    | string | YAML fragment for this view                               |

**URI pattern**

```
cube.<instance_slug>.view.<view_name>
```

Example: `cube.production.view.orders_overview`

## Cube dimension (`cube_dimension`)

Dimensions are observed under their parent cube or view.

| Property                  | Type   | Description                                                                                                                      |
| ------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------- |
| `name`                    | string | Dimension title from schema, or dimension name when no title is set                                                              |
| `type`                    | string | Always `cube_dimension`                                                                                                          |
| `native_id`               | string | Fully qualified member id (`{cube_name}.{dimension_name}` for cube-scoped members, or view-qualified id for view-scoped members) |
| `description`             | string | Dimension description when present in schema                                                                                     |
| `raw_code`                | string | YAML fragment for this dimension                                                                                                 |
| `no_compiled_code_reason` | string | Reason column-level lineage could not be resolved, when applicable                                                               |

**URI pattern**

```
<cube or view URI>.dimension.<dimension_name>
```

Example: `cube.production.cube.orders.dimension.status`

## Cube measure (`cube_measure`)

Measures are observed under their parent cube or view.

| Property                  | Type   | Description                                                                                                                    |
| ------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------ |
| `name`                    | string | Measure title from schema, or measure name when no title is set                                                                |
| `type`                    | string | Always `cube_measure`                                                                                                          |
| `native_id`               | string | Fully qualified member id (`{cube_name}.{measure_name}` for cube-scoped members, or view-qualified id for view-scoped members) |
| `description`             | string | Measure description when present in schema                                                                                     |
| `raw_code`                | string | YAML fragment for this measure                                                                                                 |
| `no_compiled_code_reason` | string | Reason column-level lineage could not be resolved, when applicable                                                             |

**URI pattern**

```
<cube or view URI>.measure.<measure_name>
```

Example: `cube.production.cube.orders.measure.count`

## Relationships

Each row is one relationship edge, written in the canonical direction for its family. Use the predicate in each heading to search for these relationships in EQL.

### Containment (`has parent` / `has child`)

| Source type      | Relationship | Target type       | Notes                                                   |
| ---------------- | ------------ | ----------------- | ------------------------------------------------------- |
| `cube_cube`      | has parent   | `cube_deployment` | Only when **Instance slug** is configured on the source |
| `cube_view`      | has parent   | `cube_deployment` | Only when **Instance slug** is configured on the source |
| `cube_dimension` | has parent   | `cube_cube`       | Cube-scoped members                                     |
| `cube_dimension` | has parent   | `cube_view`       | View-scoped members                                     |
| `cube_measure`   | has parent   | `cube_cube`       | Cube-scoped members                                     |
| `cube_measure`   | has parent   | `cube_view`       | View-scoped members                                     |

### Lineage (`has upstream` / `has downstream`)

| Source type | Relationship | Target type | Notes                                                                                                             |
| ----------- | ------------ | ----------- | ----------------------------------------------------------------------------------------------------------------- |
| `cube_cube` | has upstream | `table`     | Warehouse table from `sql_table` on the cube, qualified with the source's default database and schema when needed |
| `cube_cube` | has upstream | `cube_cube` | Joined cubes from `joins` in the cube schema, when the joined cube is observed                                    |
| `cube_view` | has upstream | `cube_cube` | Underlying cubes referenced by the view                                                                           |

### Field-level lineage (`has upstream_fields` / `has downstream_fields`)

| Source type      | Relationship         | Target type      | Notes                                                                                                                                                       |
| ---------------- | -------------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `cube_dimension` | has upstream\_fields | `column`         | Warehouse columns referenced in member SQL, filters, or case branches                                                                                       |
| `cube_dimension` | has upstream\_fields | `cube_dimension` | Cube members referenced in member SQL; for view members, the underlying cube dimension; for join keys, the joined cube's members referenced in the join SQL |
| `cube_dimension` | has upstream\_fields | `cube_measure`   | Cube members referenced in member SQL                                                                                                                       |
| `cube_measure`   | has upstream\_fields | `column`         | Warehouse columns referenced in member SQL, filters, or case branches                                                                                       |
| `cube_measure`   | has upstream\_fields | `cube_dimension` | Cube members referenced in member SQL                                                                                                                       |
| `cube_measure`   | has upstream\_fields | `cube_measure`   | Cube members referenced in member SQL; for view members, the underlying cube measure                                                                        |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.euno.ai/sources/business-intelligence/cube-core-integration/cube-core-integration-discovered-resources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.