Hosted edition
Managing Instances
An "instance" in ORDSwatch is one running ORDS server process that an agent monitors on your behalf.
Adding an instance
Most instances appear automatically once an agent is enrolled and reports in (see Agents). To add one manually:
- Go to Instances → Add Instance
- Choose the agent that will monitor it (the agent must already be enrolled and connected)
- Fill in the instance details:
| Field | Required | Description |
|---|---|---|
| Name | Friendly display name | |
| Host | Yes | Hostname or IP the ORDS process listens on |
| Port | Yes | HTTP port |
| Health check path | Defaults to /ords/_/healthcheck |
|
| Tags | Free-text labels for filtering/grouping |
- Save. The instance shows as Unknown (gray) until the agent's next health check tick reports a result — usually within 15 seconds.
Plan limits
Your plan caps how many instances you can add:
| Plan | Instance limit |
|---|---|
| Free | Up to 1 |
| Starter | Up to 3 |
| Professional | Up to 10 |
| Enterprise | Up to 20 included, then $8/month each |
If you're at your limit, Add Instance shows an upgrade prompt instead of the form. See Billing and Plans.
Editing an instance
Click an instance, then Edit. You can change its display name, tags, and grouping at any time. Operational fields (paths to the ORDS binary, config directory, log directory) are managed on the agent side and shown read-only unless you have operator/admin access.
Starting, stopping, restarting
From an instance's detail panel, operators and admins can trigger Start, Stop, or Restart. The command is sent to the owning agent over its live connection; if the agent is offline, the action fails immediately with a clear error rather than hanging.
Viewers can see instance status but cannot trigger these actions — see Users and Roles.
Removing an instance
Instances → (instance) → Remove. This stops ORDSwatch from monitoring it and deletes its history going forward. It does not stop or uninstall the ORDS process itself — that's a separate action (see above) if you want it done first.
Related
- Config Deploy — push configuration changes to an instance
- Historical Data and Reports — uptime history per instance