Create a Monitor

Go to Product

Create a new monitor.

Options

Organization Id or Slug
The ID or slug of the organization the resource belongs to.
Body

Request body which must comply to the following JSON Schema:

{
  "required" : [ "name", "type" ],
  "type" : "object",
  "properties" : {
    "name" : {
      "maxLength" : 128,
      "type" : "string",
      "description" : "Name of the monitor. Used for notifications."
    },
    "type" : {
      "type" : "string",
      "description" : "* `cron_job` - cron_job",
      "enum" : [ "cron_job" ]
    },
    "slug" : {
      "maxLength" : 50,
      "pattern" : "^(?![0-9]+$)[a-z0-9_\\-]+$",
      "type" : "string",
      "description" : "Uniquely identifies your monitor within your organization. Changing this slug will require updates to any instrumented check-in calls."
    },
    "status" : {
      "type" : "string",
      "description" : "Status of the monitor. Disabled monitors will not accept events and will not count towards the monitor quota.\n\n* `active` - active\n* `disabled` - disabled",
      "default" : "active",
      "enum" : [ "active", "disabled" ]
    },
    "owner" : {
      "type" : "string",
      "description" : "The ID of the team or user that owns the monitor. (eg. user:51 or team:6)",
      "nullable" : true
    },
    "is_muted" : {
      "type" : "boolean",
      "description" : "Disable creation of monitor incidents"
    }
  },
  "description" : "Allows parameters to be defined in snake case, but passed as camel case.\n\nErrors are output in camel case."
}
Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

  • Alert Rule:
  • Id:
  • Name:
  • Slug:
  • Status:
  • Is Muted:
  • Type:
  • Config:
  • Date Created:
  • Project:
  • Environments:
  • Owner:

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.