Skip to content
GOCUX
Documentation
GOCUX / Documentationmonitor api

Move monitoring into Pulse

Translate monitoring intent and lifecycle into GoCux definitions and occurrences.

Translate monitoring intent and lifecycle into GoCux definitions and occurrences.

Practical procedure

  1. Map the old monitor’s question, schedule and source selection to a GoCux project objective and approved Knowledge sources.
  2. Choose the supported materiality rule and a real notification mode. Create and approve a definition instead of importing an old service’s run identifier as a GoCux identifier.
  3. Establish a fresh baseline and compare representative occurrences before retiring the old workflow. Preserve export history with its original service identity.

Define an evidence-backed Pulse monitor

Pulse monitors track an objective against selected Knowledge sources. A definition records cadence, timezone, source policy, materiality rule and notification mode. Review and approve the exact definition version before running it. An occurrence records a particular run; it is distinct from the monitor definition and from any resulting email delivery.

Contract example

Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.

GET /pulse/monitors?projectId=project-id — inspect available monitor definitions

GET /pulse/monitors/{monitor_id}
GET /pulse/monitors/{monitor_id}/occurrences
GET /pulse/occurrences/{occurrence_id}

Inspect the result

Inspect occurrence state and available evidence before reporting a change. A new or missing source passage can change the support for a value even when the displayed value is unchanged. Notification mode can be none or email; choosing email is not evidence that delivery is configured or that a message reached its recipient.

What to keep explicit

External web crawling, callback delivery and snapshot semantics do not transfer automatically. Document the differences that affect the meaning of a reported change.

Handle incomplete and refused work

Creation requires at least one unique Knowledge source identifier. Decisions and transitions use explicit version checks and Idempotency-Key. A stale definition or a monitor that is not active can return 409. A 503 is unavailable monitor storage or materialization, not a statement that nothing changed. Pause or archive intentionally when the monitoring objective ends.

Bring this workflow into your workspace.

Set the scope. Review the evidence. Approve the steps that need it.

Open the workspace

Keep exploring