Elementary

Euno's Elementary Cloud integration surfaces active data quality incidents directly on impacted resources (dbt_model, dbt_source, warehouse table, and column). Elementary remains the source of truth for incidents — Euno connects to Elementary Cloud and keeps resource-level indicators in sync for discovery and filtering.

Only active incidents are shown in Euno:

• open

• acknowledged

Incidents in terminal states are not fetched, stored, or displayed.

The integration does not create new resource types. It enriches existing dbt and warehouse resources that are already present in Euno from other source integrations.

Prerequisites

• An Elementary Cloud account with API access.

• A bearer token and Environment ID from Elementary Cloud.

• dbt and/or warehouse resources already observed in Euno so incidents can be attached.

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. Incidents from seeds, snapshots, schema tests, custom generic tests outside these sets, or other asset types are not imported.

Stage 1: Configure Elementary Cloud

Step 1: Obtain Elementary Cloud credentials

1. Log in to your Elementary Cloud account.

2. Navigate to Settings → API (or your account's token management page).

3. Generate a new API token (bearer token).

4. Copy the token — it will be needed for Euno configuration and cannot be retrieved again.

5. Note your Environment ID — this identifies the Elementary environment whose incidents Euno will sync. It is visible in the Elementary Cloud UI under your environment settings.

Stage 2: Configure New Elementary Source in Euno

Step 1: Access the Sources Page

1. Go to the Sources page in Euno.

2. Click Add New Source and select Elementary Cloud from the list of supported platforms.

Step 2: General Configuration

Asterisk (*) means a mandatory field.

Configuration	Description
Name*	Enter a name for your Elementary source (e.g., "Elementary - Data Quality").
Bearer Token*	The API token generated in Step 1. Stored securely in Euno.
Environment ID*	The Elementary environment ID to query. Scopes all incident fetches to a single environment.
Elementary MCP Endpoint	Base URL of the Elementary MCP API. Defaults to https://prod.api.elementary-data.com/mcp/. Change this only if your Elementary account uses a custom or self-hosted endpoint.
Warehouse mapping	Optional mapping of Elementary database.schema identifiers to Euno database.schema identifiers. Use this when Elementary reports warehouse coordinates that differ from those in Euno (e.g., due to connection aliases). Keys are matched case-insensitively against the database.schema reported for each incident. Keys wrapped in /…/ are treated as regular expressions. Example: {"elem_db.prod": "euno_db.prod", "/elem_db\\.(.*)/": "euno_db.$1"}.

Step 3: Schedule

• Enable the Schedule option.

• Choose:

  1. Weekly: Set specific days and times.

  2. Hourly: Define the interval in hours (e.g., every 4 hours).

Recommended: Schedule the Elementary integration to run frequently (every 1–4 hours) so that active incident state stays close to real-time. Manual runs are also supported.

Step 4: Resource Cleanup

The Elementary integration requires Immediate Cleanup.

• Immediate Cleanup: incidents not present in the most recent successful integration run are removed from all attached resources immediately. This keeps Euno's view aligned with the set of currently active incidents in Elementary.

Immediate Cleanup is the only supported cleanup mode for this integration.

Step 5: Save Configuration

Click the Test & Save button to complete the setup. Euno will:

1. Connect to Elementary Cloud using the provided bearer token.

2. Verify access by fetching the current list of active incidents for the configured environment.

3. Save the configuration if validation passes.

If the test fails, check that the bearer token is valid and that the environment ID matches an environment visible in your Elementary Cloud account.

What Euno Discovers

The Elementary integration does not create new resource types. Instead, it enriches existing dbt_model, dbt_source, table, and column resources with active-incident properties. For detailed information about the enriched properties, see Elementary Integration Discovered Resources.