# Monte Carlo Commands

## Overview

Paradime Bolt integrates with by Montecarlo feeding the [manifest file](https://docs.getdbt.com/reference/artifacts/manifest-json), [run results file](https://docs.getdbt.com/reference/artifacts/run-results-json), and optionally, a file containing the logs generated by dbt™ during command execution. This will make dbt™ metadata available within the Monte Carlo dashboard.

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2FRZKI2P1msYRBHZJLMit6%2Fimage.png?alt=media&#x26;token=790300f1-c26b-4a4b-8922-cabda2dbb72b" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}

#### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* Configure the [**Monte Carlo integration.**](https://docs.paradime.io/app-help/documentation/integrations/observability/monte-carlo)
* Whenever a dbt command is executed, files in the `target` directory will be overwritten. So you will need to run the MC CLI command after each dbt command.
  {% endhint %}

{% hint style="info" %}
**Note**

If you want to enable Paradime to automatically send all dbt™ artifacts for all runs, you can choose to set the variable[`RUN_MONTECARLO_UPLOAD`](https://docs.paradime.io/app-help/integrations/observability/monte-carlo#step-6-enable-the-integration) to `TRUE`.
{% endhint %}

## import dbt-run[#](https://clidocs.getmontecarlo.com/#montecarlo-import-dbt-run)

Import dbt run artifacts CLI

```
montecarlo import dbt-run [OPTIONS]
```

| Flag              | Type               | Description                                                                                                                                                                    |
| ----------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `--project-name`  | *`Optional, TEXT`* | <p>Project name (perhaps a logical group of dbt models, analogous to a workspace in Paradime) </p><p><br>- Default: <em>default-project</em></p>                               |
| `--job-name`      | *`Optional, TEXT`* | <p>Job name (perhaps a logical sequence of dbt executions, analogous to a schedule name in Paradime)</p><p><br>- Default: <em>default-job</em></p>                             |
| `--manifest`      | *`Required, TEXT`* | Path to the dbt manifest file (manifest.json)                                                                                                                                  |
| `--run-results`   | *`Required, TEXT`* | Path to the dbt run results file (run\_results.json)                                                                                                                           |
| `--logs`          | *`Required, TEXT`* | Path to a file containing dbt run logs                                                                                                                                         |
| `--connection-id` | *`Required, TEXT`* | <p>Identifier of warehouse or lake connection to use to resolve dbt models to tables. </p><p><em>Required if you have more than one warehouse or lake connection.</em><br></p> |

{% hint style="info" %}
Check [Monte Carlo's CLI Reference](https://clidocs.getmontecarlo.com) for a complete list of CLI arguments.
{% endhint %}

***

Now, let's learn how to configure the [Trigger Types](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/trigger-types) of a Bolt Schedule. &#x20;


---

# Agent Instructions: 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:

```
GET https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/command-settings/monte-carlo-commands.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.