> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-mcp/tool-reference/evaluations-and-monitoring/evals-monitors-create.md).

# evals\_monitors\_create

Create a monitor that samples future project runs for one evaluator.

**Effect:** This call saves data or changes configuration. Review the behavior below before using it.

## Inputs

| Name                    | Type    | Requirement | Description                                                                                                       |
| ----------------------- | ------- | ----------- | ----------------------------------------------------------------------------------------------------------------- |
| `project_id`            | string  | Required    | ID returned by `projects_list`; use a project in the active organization.                                         |
| `evaluator_id`          | string  | Required    | Evaluator ID returned by evaluator discovery or creation.                                                         |
| `name`                  | string  | Optional    | Resource name.                                                                                                    |
| `sampling_rate`         | number  | Optional    | Fraction of future runs to sample: greater than 0 and at most 0.3. Default 0.3 (30%). For example, 0.1 means 10%. |
| `max_runs_daily`        | integer | Optional    | Daily sampled-run cap: 1–1000. Default 1000. Count resets by UTC day.                                             |
| `notifications_enabled` | boolean | Optional    | Default `true`. Enables monitor notifications; use `false` to disable them.                                       |

## Example

These are MCP tool arguments, not an HTTP request body. Replace bracketed IDs with values returned from your account.

```json
{
  "project_id": "<project-id>",
  "evaluator_id": "<evaluator-id>",
  "sampling_rate": 0.1,
  "max_runs_daily": 100,
  "notifications_enabled": false
}
```

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "monitor": {
    "monitor_id": "<monitor-id>",
    "sampling_rate": 0.1,
    "max_runs_daily": 100,
    "enabled": true
  }
}
```

## Behavior

Optional name, sampling\_rate, max\_runs\_daily and notifications\_enabled let you configure sampling, daily limits and notifications.

Creates continuous evaluation of sampled future runs and may incur judge costs.

## Troubleshooting

Use a compatible evaluator that does not require a reference output. Keep sampling and daily-cap values within the documented limits.

## Related resources

[Evaluations and monitoring](https://docs.stackai.com/stackai-mcp/tool-reference/evaluations-and-monitoring.md)

[Monitor production quality](https://docs.stackai.com/stackai-mcp/workflow-recipes/monitor-production-quality.md)

[Connection, permissions, pagination, and recovery](https://docs.stackai.com/stackai-mcp/best-practices-and-troubleshooting.md)


---

# 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.stackai.com/stackai-mcp/tool-reference/evaluations-and-monitoring/evals-monitors-create.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.
