Monitor
A Monitor is a scheduled check on something outside a Startup’s control, such as uptime, a Keyword’s rank or an AI answer, recording Events.
Properties
| Property | Type | Required | Description |
|---|---|---|---|
kind | string | required | internal watches the Startup’s own routes and jobs; outside watches the world, such as a rival’s price. |
target | string | required | What it checks: a route, a Domain, a Keyword, a prompt or a page. |
every | string | How often it runs, such as 1m or 1d. | |
lastResult | string | The result of its latest check. |
Object
{
"$id": "https: //api.sb/ kilnbakery.com/ monitors/ monitor_1",
"$type": "Monitor",
"kind": "internal",
"target": "/health",
"every": "1m",
"lastResult": "passing"
}Relationships
- A Monitor opens many Incidents: a failing internal Monitor opens an Incident, which names the Monitor that saw it first.
opens, inversemonitor.
Verbs
createCreates a Monitor.POST /{namespace}/monitorsgetReturns one Monitor by id.GET /{namespace}/monitors/{id}listReturns Monitors, newest first, one page at a time.GET /{namespace}/monitorsupdateChanges the given properties of a Monitor.PATCH /{namespace}/monitors/{id}checkCheck runs a Monitor once now from several regions and records the result as an Event.POST /{namespace}/monitors/{monitor}/check
Permissions
Which Access level may call each Verb. One-way Verbs wait their delay window.
| Operation | owner | admin | member | viewer |
|---|---|---|---|---|
Monitor.create | Yes | Yes | Yes | No |
Monitor.get | Yes | Yes | Yes | Yes |
Monitor.list | Yes | Yes | Yes | Yes |
Monitor.update | Yes | Yes | Yes | No |
Monitor.check | Yes | Yes | Yes | No |
Call it
Check the latest monitor.Example
A scheduling app runs an outside Monitor that asks three answer engines "best scheduling app for clinics" once a day. When the app drops out of an answer, the Monitor records an Event and the Marketing Lead sees it.