InOrbitdocs
Sign in
Docs
Have a token? Manage tokens in the console
PATCH
/v1/accounts/orgs/{org_id}/monitors/{monitor_id}

Changes its name, interval, expectation or failure threshold, or pauses (state: paused) and resumes it. Fields left out stay as they are.

Needs scope connections:write.

Authorization

bearer
headerAuthorizationBearer <token>

An access token from the identity provider: a person's, or a customer's from the client credentials grant with an API key (docs.inorbit.hr). The gateway verifies it; the audience is iohr-api.

Path Parameters

org_id*string

The account's id: org in GET /v1/me.

monitor_id*string

The monitor's id, mon_ and a ULID, from List monitors.

Header Parameters

idempotency-key?string

Makes a retry safe: a repeat with the same key and the same body within a day answers what the first call did (with Idempotency-Replayed: true) instead of running again; the same key with another body is 422 unprocessable. 1 to 255 visible characters; a UUID is a good one.

Length1 <= length <= 255

Request Body

iohr.connections.v1.UpdateMonitorRequest; path variables override their fields

application/json
  1. body

iohr.connections.v1.UpdateMonitorRequest

category?string
fail_after?integer
Formatint32
interval_secs?integer
Formatint32
monitor_id?string
name?string
org_id?string
params?

iohr.connections.v1.MonitorParams

rfc?string
slo_target?number
Formatdouble
state?string
tags?

iohr.connections.v1.MonitorTags

Response Body

iohr.connections.v1.UpdateMonitorResponse

application/json
  1. response

iohr.connections.v1.UpdateMonitorResponse

monitor?

iohr.connections.v1.Monitor

import { ApiError, Public } from "@inorbithr/sdk";// Reads INORBIT_TOKEN, or INORBIT_KEY_ID and INORBIT_KEY_SECRET.const api = Public.fromEnv();try {  const { value } = await api.connections.updateMonitor("<org_id>", "<monitor_id>", {    category: "<category>",    name: "<name>",    rfc: "<rfc>",    state: "<state>",  });  console.log(value);} catch (e) {  if (!(e instanceof ApiError)) throw e;  console.error(`${e.code}: ${e.problem} (request id ${e.raw.requestId})`);}

npm install @inorbithr/sdk. Calls the package's public surface; an operation newer than your package needs the next release or a client generated for your account. The SDKs.

{  "monitor": {    "agent_id": "string",    "category": "string",    "check": {      "expect": {        "max_ms": 0,        "status": 0,        "valid_for_days": 0      },      "key": "string",      "notify": true,      "refuse_by": "string",      "service": "string",      "surface": "string",      "target": {        "host": "string",        "port": 0,        "tls": true,        "url": "string"      }    },    "connection_id": "string",    "created_at": "string",    "executor": {      "agent_id": "string",      "kind": "string"    },    "fail_after": 0,    "health": "string",    "interval_secs": 0,    "last_run_at": "string",    "managed_by": "string",    "monitor_id": "string",    "name": "string",    "next_run_at": "string",    "params": {      "expect_status": 0,      "max_ms": 0,      "path": "string"    },    "paused_reason": "string",    "rfc": "string",    "slo_target": 0.1,    "state": "string",    "tags": {      "property1": "string",      "property2": "string"    }  }}

Create a monitor POST

Runs the connection's `check` every `interval_secs` (60 at least) from the connection's executor, our cloud or your agent. `fail_after` failures in a row (1 to 5, 2 when 0) make it `down`. Needs scope `connections:write`.

Delete a monitor DELETE

Stops the monitor and deletes it with its runs. Needs scope `connections:write`.