> 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/data-observability/elementary-integration/elementary-discovered-resources.md).

# Elementary Integration Discovered Resources

### Overview

The Elementary integration does not create new resource types. It enriches existing **`dbt_model`**, **`dbt_source`**, **`table`**, and **`column`** resources with active-incident properties from Elementary Cloud.

The integration does not discover or import warehouse hierarchy — those resources must already exist in Euno from another source integration (typically a dbt or warehouse integration).

Only incidents in active states (`open`, `acknowledged`) are shown in Euno. Incidents in terminal states are not stored or displayed.

Only incidents originating from **dbt tests on dbt model or dbt source assets** are supported. Supported test types are built-in dbt tests (`not_null`, `unique`, `relationships`, `accepted_values`) and `dbt_utils` tests (e.g. `dbt_utils.not_null_proportion`, `dbt_utils.recency`). Incidents from seeds, snapshots, schema tests, custom generic tests outside these sets, or other asset types are not imported.

### dbt Model, dbt Source, Table, and Column — Elementary Incident Properties

When a dbt model, dbt source, warehouse table, or column is affected by one or more active Elementary incidents, the following properties are added to that resource:

| Property                 | Description                                                                               | Applicable resources                         |
| ------------------------ | ----------------------------------------------------------------------------------------- | -------------------------------------------- |
| `has_active_incident`    | `true` when the resource has at least one attached active incident; `false` when cleared. | `dbt_model`, `dbt_source`, `table`, `column` |
| `active_incidents_count` | Count of currently active incidents attached to this resource.                            | `dbt_model`, `dbt_source`, `table`, `column` |
| `incidents`              | Structured list of active incident details (see Incident details below).                  | `dbt_model`, `dbt_source`, `table`, `column` |

Column-level incidents appear on the matching **`column`** when Euno can link the incident to a warehouse table and column that already exist in your catalog. Otherwise, the incident is shown on the parent **`dbt_model`**, **`dbt_source`**, or **`table`**.

### Incident details

Each entry in the `incidents` list includes the information Euno displays from Elementary Cloud.

#### Identity

| Field           | Description                                                                                     |
| --------------- | ----------------------------------------------------------------------------------------------- |
| `incident_id`   | Unique identifier of the incident in Elementary Cloud.                                          |
| `asset_id`      | Elementary asset ID for the affected dbt model, dbt source, table, or column.                   |
| `incident_type` | `model` for a whole dbt model, `source` for a dbt source, `column` for a column-level incident. |

#### State

| Field      | Description                                                                                                     |
| ---------- | --------------------------------------------------------------------------------------------------------------- |
| `status`   | One of `open`, `acknowledged`. Closed or fixed incidents are not shown in Euno.                                 |
| `severity` | One of `critical`, `high`, `normal`, `low`. Elementary values such as `medium` or `warning` appear as `normal`. |

#### Time

| Field        | Description                                       |
| ------------ | ------------------------------------------------- |
| `created_at` | When the incident was first opened in Elementary. |
| `updated_at` | When the incident was last updated in Elementary. |

#### Test information

| Field       | Description                                                            |
| ----------- | ---------------------------------------------------------------------- |
| `test_id`   | Identifier of the dbt test that produced the incident, when available. |
| `test_name` | Name of the failing test (e.g. `not_null`, `dbt_utils.recency`).       |
| `test_type` | `builtin` for core dbt tests; `dbt_utils` for `dbt_utils.*` tests.     |

#### Assignment and ticketing

| Field         | Description                                                                     |
| ------------- | ------------------------------------------------------------------------------- |
| `assigned_to` | Elementary user the incident is assigned to, when set.                          |
| `ticket_url`  | Link to an external ticket (Jira, Linear, etc.), when configured in Elementary. |
| `ticket_id`   | External ticket identifier, when configured in Elementary.                      |

#### Affected asset location

| Field         | Description                                                     |
| ------------- | --------------------------------------------------------------- |
| `name`        | Display name of the incident (Elementary message or test name). |
| `database`    | Warehouse database for the affected asset.                      |
| `schema`      | Warehouse schema for the affected asset.                        |
| `object_name` | Table or model name for the affected asset.                     |
| `column_name` | Column name for column-level incidents; empty otherwise.        |

### How incidents are matched to Euno resources

Euno uses the warehouse coordinates from each incident (`database`, `schema`, `object_name`, and `column_name` when present), together with optional **warehouse mapping** in the source settings, to attach incidents to resources already in your catalog:

1. **dbt model or source** — match a `dbt_model` or `dbt_source` by database, schema, and model or source name. If more than one resource could match, Euno uses the Elementary asset path to choose the right one.
2. **Warehouse table** — match a `table` using the same database, schema, and table name, using the warehouse connection from the matched dbt resource when available.
3. **Warehouse column** — when the incident names a column and a matching `table` exists in Euno, attach the incident to the corresponding `column`.

Incidents that cannot be linked to a resource already in Euno are skipped. The integration run report lists how many incidents were skipped and why.

### Warehouse mapping

If Elementary reports `database.schema` values that differ from what Euno uses for the same warehouse (for example, because of connection aliases), configure **warehouse mapping** in the source settings.

Keys are matched **case-insensitively** against the `database.schema` reported for each incident. Keys wrapped in `/…/` are treated as regular expressions; you can use `$1`, `$2`, and so on in the mapped value to reuse parts of the key.

```json
{
  "elem_db.prod_schema": "euno_db.prod_schema",
  "/elem_db\\.(.*)/": "euno_db.$1"
}
```

In the example above, the first entry maps an exact `database.schema` pair, and the second remaps all schemas under `elem_db` to their equivalent under `euno_db`.

### Relationships

The Elementary integration does not create relationships between resources. It adds incident properties to existing resources. Lineage and hierarchy from your other sources are unchanged.

### Usage in EQL

You can filter and search by Elementary incident properties in Euno's search and EQL:

**Examples**:

```
# dbt models with at least one active Elementary incident
has_active_incident = true and type = "dbt_model"

# dbt sources with at least one active Elementary incident
has_active_incident = true and type = "dbt_source"

# Warehouse columns currently flagged by Elementary
has_active_incident = true and type = "column"

# Resources with more than 2 active incidents
active_incidents_count > 2

# Warehouse tables touched by Elementary incidents
has_active_incident = true and type = "table"
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.euno.ai/sources/data-observability/elementary-integration/elementary-discovered-resources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.