Monte Carlo

Euno's Monte Carlo integration surfaces active data quality alerts directly on the impacted table resources and introduces the originating Monte Carlo monitor as a first-class resource in the Euno data model.

Monte Carlo remains the source of truth for alerts. Euno retrieves alert payloads via the Monte Carlo GraphQL API and computes a set of resource-level indicators for discovery and filtering.

Only active alerts are ingested:

• Investigating

• No Status (newly opened, not yet triaged)

Alerts in terminal states (Fixed, No Action Needed, False Positive, Expected, Resolved, Closed, Acknowledged) are not fetched, stored, or displayed.

Euno's Monte Carlo integration supports auto-discovery of:

• montecarlo_account — top-level account container holding warehouse connection metadata

• montecarlo_monitor — each Monte Carlo monitor that has produced at least one active alert

In addition, the integration enriches existing table resources with active-alert properties. It does not discover or import warehouse hierarchy from Monte Carlo.

Prerequisites

• A Monte Carlo account with at least one configured warehouse connection.

• Administrator access to Monte Carlo to create an Account Service Key.

• The tables you want to enrich with alerts must already exist in Euno from another source integration (Snowflake, BigQuery, dbt, etc.). Euno resolves alerts to existing resources — it does not create warehouse hierarchy from Monte Carlo.

Stage 1: Configure Monte Carlo

Step 1: Create a Monte Carlo Account Service Key

1. Log in to your Monte Carlo account as an administrator.

2. Navigate to Settings → API.

3. Create a new Account Service Key.

4. Copy the API Key ID and API Key Secret — you'll need these for Euno configuration.

Account-level token required when SSO is enabled: If your Monte Carlo account uses SSO, you must provide an account-level Account Service Key (not a user-scoped key) for this integration to work. User-scoped tokens issued under SSO will not authenticate successfully against the headless GraphQL API used by the integration.

Stage 2: Configure New Monte Carlo Source in Euno

Step 1: Access the Sources Page

1. Go to the Sources page in Euno.

2. Click on Add New Source and select Monte Carlo from the list of supported platforms.

Step 2: General Configuration

Asterisk (*) means a mandatory field.

Configuration	Description
Name*	Enter a name for your Monte Carlo source (e.g., "Monte Carlo - Data Observability").
MCD API Key ID*	Account Service Key ID from Step 1. Sent on every request as the x-mcd-id header.
MCD API Key Secret*	Account Service Key secret token from Step 1. Sent on every request as the x-mcd-token header. Stored securely.
Monte Carlo API Endpoint	Base URL of the Monte Carlo GraphQL API. Defaults to https://api.getmontecarlo.com/graphql. Override only if your account uses a custom endpoint.
Warehouse Mapping	Optional JSON mapping of Monte Carlo warehouse identifiers to Euno source URIs. Required only in multi-warehouse setups where automatic matching is ambiguous. Contact Euno support for the expected format.

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 Monte Carlo integration to run every 4 hours so active alert state stays close to real-time. Manual runs are also supported.

Step 4: Resource Cleanup

The Monte Carlo integration uses Immediate Cleanup for alert attachments and montecarlo_monitor resources.

• Immediate Cleanup: alerts and monitor resources not detected in the most recent successful integration run are removed. This ensures Euno's view stays aligned with the set of currently active alerts in Monte Carlo.

Step 5: Save Configuration

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

1. Authenticate to the Monte Carlo GraphQL API using the provided API Key ID and Secret.

2. Verify access by issuing a small probe query.

3. Save the configuration if validation passes.

If the test fails, review the error message and verify your credentials. The most common cause of failure is a user-scoped token in an SSO-enabled account — see the note in Step 1.

What Euno Discovers

• montecarlo_account — The top-level Monte Carlo account container. Holds warehouse connection metadata and the warehouse-to-Euno mapping context used to resolve alerts to the correct resources.

• montecarlo_monitor — A Monte Carlo data quality monitor. One resource is created per monitor returned by Monte Carlo's getMonitors API. Stores the full monitor payload and its list of active alerts.

In addition, existing table resources are enriched with alert properties when they are the impacted asset of one or more active Monte Carlo alerts.

For detailed information about discovered resources and their indexed properties, see Monte Carlo Integration Discovered Resources.