Create an Auto Monitor Setup
Auto-monitor-setups
Create an Auto Monitor Setup
Trigger a process that attempts to create a Traceloop monitor using the provided selector criteria
POST
Create an Auto Monitor Setup
An auto monitor setup is an asynchronous process that attempts to create a Traceloop monitor based on theDocumentation Index
Fetch the complete documentation index at: https://www.traceloop.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
selector you provide. The selector is matched against your incoming spans — when a match is found, the monitor is created and the specified evaluators begin running on those spans.
All API requests require authentication. Pass your API key as a Bearer token in the
Authorization header.
See Authentication for details.Request Body
Unique identifier for the auto monitor setup. Used to reference it in future requests (get, update, delete).Example:
"my-agent-monitor-1"List of evaluator slugs to run on matched spans. Must contain at least one evaluator.Example:
["answer-relevancy", "toxicity-detector"]See the full list of available slugs in the Evaluator Slugs reference.An array of filter rules used to match spans. Each rule specifies an attribute key, a value to match, and a source indicating where the attribute lives. Only spans matching all provided rules will be evaluated.Each rule has the following fields:
All available span and resource attributes can be found in your Traceloop traces page.
| Field | Type | Required | Description |
|---|---|---|---|
key | string | Yes | The attribute key to filter on (e.g., gen_ai.system, service.name) |
value | string | Conditional | The value to match against. Required for equals, not_equals, contains, not_contains operators |
values | string[] | Conditional | List of values to match against. Required for in, not_in operators |
source | string | Yes | Where the attribute lives: span_attributes or resource_attributes |
operator | string | No | Comparison operator. Defaults to equals. One of: equals, not_equals, contains, not_contains, exists, not_exists, in, not_in |
Example Request
Response
201 Created
Returns the created auto monitor setup object. Theinit_rules array reflects the stored selector — same shape as the input selector.
The status field indicates the current state of the setup process:
| Status | Description |
|---|---|
pending | The setup has been created and is queued for processing |
in_progress | The setup is actively being processed |
waiting_for_spans | The setup is ready and waiting for enough spans to be received before attempting to process |
completed | All monitors have been successfully created |
partial | Some monitors were created but others failed |
failed | The setup process failed |
400 Bad Request
Returned when the request body is invalid (e.g. missing required fields or emptyevaluators array).

