Title: Create monitor
Open Graph Title: Create monitor
X Title: Create monitor
Description: Creates a monitor. Fields left out take their defaults; `cost_type` defaults to `REAL_COST`. For what each cost type measures, see [Cost Types](/docs/cost-types). `CUSTOM_COST` is a cost calculation defined for your organization. If another monitor in your organization already has the same `filter_set`, `group_by`, `threshold`, and `cost_type`, the call returns `409` without creating a monitor, and `error.existing_id` names the existing one. A client that retries after a lost response can use that ID to pick up the monitor its first call created. Paused monitors count as a match and deleted monitors don't. The order of values in `filter_set` and `group_by` doesn't matter, and `monitor_name`, `description`, and `is_enabled` aren't compared. `group_by` accepts at most one Dimension. Notification channels aren't set here; set them afterward with [Update monitor notifications](/reference/updatemonitornotifications). Field validation failures return `422` with a `details` list. CloudZero records the change in the activity log, attributed to "Set via API", after saving it. If that log write fails, the monitor is still created.
Open Graph Description: Creates a monitor. Fields left out take their defaults; `cost_type` defaults to `REAL_COST`. For what each cost type measures, see [Cost Types](/docs/cost-types). `CUSTOM_COST` is a cost calculation defined for your organization. If another monitor in your organization already has the same `filter_set`, `group_by`, `threshold`, and `cost_type`, the call returns `409` without creating a monitor, and `error.existing_id` names the existing one. A client that retries after a lost response can use that ID to pick up the monitor its first call created. Paused monitors count as a match and deleted monitors don't. The order of values in `filter_set` and `group_by` doesn't matter, and `monitor_name`, `description`, and `is_enabled` aren't compared. `group_by` accepts at most one Dimension. Notification channels aren't set here; set them afterward with [Update monitor notifications](/reference/updatemonitornotifications). Field validation failures return `422` with a `details` list. CloudZero records the change in the activity log, attributed to "Set via API", after saving it. If that log write fails, the monitor is still created.
X Description: Creates a monitor. Fields left out take their defaults; `cost_type` defaults to `REAL_COST`. For what each cost type measures, see [Cost Types](/docs/cost-types). `CUSTOM_COST` is a cost calculation defined for your organization. If another monitor in your organization already has the same `filter_set`, `group_by`, `threshold`, and `cost_type`, the call returns `409` without creating a monitor, and `error.existing_id` names the existing one. A client that retries after a lost response can use that ID to pick up the monitor its first call created. Paused monitors count as a match and deleted monitors don't. The order of values in `filter_set` and `group_by` doesn't matter, and `monitor_name`, `description`, and `is_enabled` aren't compared. `group_by` accepts at most one Dimension. Notification channels aren't set here; set them afterward with [Update monitor notifications](/reference/updatemonitornotifications). Field validation failures return `422` with a `details` list. CloudZero records the change in the activity log, attributed to "Set via API", after saving it. If that log write fails, the monitor is still created.
Domain: docs.cloudzero.com
{"@context":"https://schema.org","@type":"TechArticle","headline":"Create monitor","dateModified":"2026-10-22T16:23:14.000Z"}
| readme-deploy | 5.973.1 |
| readme-subdomain | cloudzero |
| readme-repo | docs-beta-cz-749934af4f1e |
| readme-project-flags | rwQE93LrI5lYOuBjZ302cg==:x3Imwt3rk2cR5YiszEVElUlw8ohZvMuTGDszeoltqZJ3m7w25/ENlpNTLQWhmDPqgOLhylzOQMTzwCuEu5eDz9eyb6pjp5W8LTO9OfbuUHmg9XYChtvbF33irnp8pUgqZ/UbqmYE5VpabcUjq3izZFX/5VjzZRmwyr0NkFRCfU8= |
| readme-version | 2.0 |
| og:site_name | CloudZero Documentation |
| twitter:card | summary_large_image |
| og:image | https://cdn.readme.io/og-image/create?type=reference&title=Create monitor&projectTitle=CloudZero Documentation&description=Creates a monitor. Fields left out take their defaults; `cost_type` defaults to `REAL_COST`. For what each cost type measures, see [Cost Types](/docs/cost-types). `CUSTOM_COST` is a cost calculation defined for your organization. If another monitor in your organization already has the same `filter_set`, `group_by`, `threshold`, and `cost_type`, the call returns `409` without creating a monitor, and `error.existing_id` names the existing one. A client that retries after a lost response can use that ID to pick up the monitor its first call created. Paused monitors count as a match and deleted monitors don't. The order of values in `filter_set` and `group_by` doesn't matter, and `monitor_name`, `description`, and `is_enabled` aren't compared. `group_by` accepts at most one Dimension. Notification channels aren't set here; set them afterward with [Update monitor notifications](/reference/updatemonitornotifications). Field validation failures return `422` with a `details` list. CloudZero records the change in the activity log, attributed to "Set via API", after saving it. If that log write fails, the monitor is still created. &logoUrl=https://files.readme.io/e7c5ff8ece6436cb3b1d3fc0648afca17d366e8b4b177a74f3ee5dcfb5eaa31c-cloudzero-logo-color-rgb.png&color=#fe552e&variant=light |
| twitter:image | https://cdn.readme.io/og-image/create?type=reference&title=Create monitor&projectTitle=CloudZero Documentation&description=Creates a monitor. Fields left out take their defaults; `cost_type` defaults to `REAL_COST`. For what each cost type measures, see [Cost Types](/docs/cost-types). `CUSTOM_COST` is a cost calculation defined for your organization. If another monitor in your organization already has the same `filter_set`, `group_by`, `threshold`, and `cost_type`, the call returns `409` without creating a monitor, and `error.existing_id` names the existing one. A client that retries after a lost response can use that ID to pick up the monitor its first call created. Paused monitors count as a match and deleted monitors don't. The order of values in `filter_set` and `group_by` doesn't matter, and `monitor_name`, `description`, and `is_enabled` aren't compared. `group_by` accepts at most one Dimension. Notification channels aren't set here; set them afterward with [Update monitor notifications](/reference/updatemonitornotifications). Field validation failures return `422` with a `details` list. CloudZero records the change in the activity log, attributed to "Set via API", after saving it. If that log write fails, the monitor is still created. &logoUrl=https://files.readme.io/e7c5ff8ece6436cb3b1d3fc0648afca17d366e8b4b177a74f3ee5dcfb5eaa31c-cloudzero-logo-color-rgb.png&color=#fe552e&variant=light |
| og:image:width | 1200 |
| og:image:height | 630 |
| dateModified | 2026-10-22T16:23:14.000Z |
| article:modified_time | 2026-10-22T16:23:14.000Z |
| og:updated_time | 2026-10-22T16:23:14.000Z |
| loadedProject | cloudzero |
Links:
Viewport: width=device-width, initial-scale=1.0