> 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 resources. It enriches existing resources with active-incident properties from Elementary Cloud:

* Enriched dbt model (`dbt_model`)
* Enriched dbt source (`dbt_source`)
* Enriched dbt column (`dbt_column`)
* Enriched table (`table`)
* Enriched column (`column`)

The integration does not discover or import warehouse hierarchy. These 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, including built-in, `dbt_utils`, renamed, and custom tests. Elementary-native automated anomaly tests and incidents from seeds, snapshots, or other asset types are not imported.

## Enriched dbt model (`dbt_model`)

A dbt model (owned by the dbt integration) that is affected by one or more active Elementary incidents receives these properties:

| Property                 | Type    | Description                                                                                                                                                                          |
| ------------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `has_active_incident`    | boolean | `true` when the resource has at least one attached active incident; `false` when cleared.                                                                                            |
| `active_incidents_count` | number  | Count of currently active incidents attached to this resource.                                                                                                                       |
| `incidents`              | object  | Structured details of the active incidents attached to this resource. See [Incident details](#incident-details). Shown on the resource **Observability** tab; not searchable in EQL. |

## Enriched dbt source (`dbt_source`)

A dbt source (owned by the dbt integration) affected by an active Elementary incident receives the same properties as an enriched `dbt_model` (`has_active_incident`, `active_incidents_count`, `incidents`).

## Enriched dbt column (`dbt_column`)

A dbt column (owned by the dbt integration) receives the same properties as an enriched `dbt_model` (`has_active_incident`, `active_incidents_count`, `incidents`) when a column-level incident names it and its parent `dbt_model` or `dbt_source` is matched.

## Enriched table (`table`)

A warehouse table (owned by the warehouse integration) receives the same properties as an enriched `dbt_model` (`has_active_incident`, `active_incidents_count`, `incidents`) when it matches the database, schema, and table name of an incident.

## Enriched column (`column`)

A warehouse column (owned by the warehouse integration) receives the same properties as an enriched `dbt_model` (`has_active_incident`, `active_incidents_count`, `incidents`) when a column-level incident names it and its parent `table` exists in Euno.

For column-level incidents, Euno attaches the incident to the matched parent `dbt_model` or `dbt_source`, and also to the matching warehouse `column` and `dbt_column` when those resources exist in the catalog. Matching warehouse `table` resources are enriched as well when resolved.

## Relationships

The Elementary integration does not create relationships. It enriches existing `dbt_model`, `dbt_source`, `dbt_column`, `table`, and `column` resources that other integrations discover. Lineage and hierarchy from your other sources are unchanged.

## Incident details

Each entry in the `incidents` property 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 (for example `not_null`, `dbt_utils.recency`).                                                                                   |
| `test_type` | `builtin` or `dbt_utils` for recognized test names; `unknown` when the name does not establish the test's origin. Unknown origin does not prevent import. |

### 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`.
4. **dbt column** — when the incident names a column and a matching `dbt_model` or `dbt_source` exists, also attach the incident to the child `dbt_column` with that name (when present in the catalog).

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`.

## Usage in EQL

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

```
# 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"

# dbt columns currently flagged by Elementary
has_active_incident = true and type = "dbt_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 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/data-observability/elementary-integration/elementary-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.