Connect Your First System
Connect equipment, select readings and build your first useful grid.
Start with one useful observation
The Guided Tour on a new grid covers a host, network devices, an equipment API, SNMP, a remote script, a live feed or an editable diagram layout. Choose one system and get a real reading before mapping the rest of the building. Use Skip Tour any time; Guided Tour in the top toolbar restarts it. All Steps jumps to a specific topic. See the full setup checklist.
Starter layouts place equipment without inventing addresses, physical connections or measurements. Rename and connect each item to match your installation. An Operations Dashboard starts clear for metric panels and playback windows linked to existing equipment.
The equipment inspector distinguishes Diagram Only, Setup Required, Connected, Connection Failed and Reporting Stale. A configured wire is not proof a cable is physically present. A stale reading is not a current healthy result.
Equipment with an API
Choose Equipment API Or Controller, enter its address and credentials, and choose the agent that can reach it. Use Server Controller (Redfish) for supported hardware controllers. Use Custom API for other equipment.
Save the connection, then choose Find Available APIs to check common OpenAPI locations and the Redfish service root using read requests. No network range scan is performed. If the device does not publish a specification at those paths, choose Import OpenAPI. Supply the document’s path on the device or upload its JSON specification. Sysavia reads the specification and lists described operations. It does not guess paths by trying commands. Local schema references are resolved; external or unresolved definitions require a resolved specification or manual review.
Select the readings and controls you want. Review their names and inputs before saving. Simple request-body schemas become labeled fields; complex bodies use a request editor. Select a read operation, refresh it, and choose a response field to publish. For example, choose ports.0.linkState instead of keeping the entire response.
Use Monitor This Reading to attach the result to equipment. Set the expected healthy value, then use that check in metrics, alerts or recovery rules. Enabling a control requires both the connection’s control toggle and the network agent’s control permission. Running one directly also requires confirmation.
Once an integration works, choose Use For Another Device to reuse its operation definitions and authentication style. Enter the new address and credentials. Credentials and enabled controls are not copied.
Equipment without a specification
Use Edit Operations to add a documented request: a friendly name, method and relative path, optional body, and the response field to extract. A manufacturer’s documented API request is the best starting point. Avoid copying browser session cookies into permanent integrations.
A web dashboard does not necessarily expose a stable API. Sysavia cannot reliably infer all actions from an arbitrary login page. Some equipment needs a vendor-specific adapter, an exported specification or a carefully configured request. Discovery does not bypass credentials, licenses or device permissions.
SNMP
Select SNMP Device, the host, execution agent and SNMP version. Use the community for v2c or the configured username, SHA authentication password and AES privacy password for v3. Choose uptime, system name or description, or enter a vendor OID.
Choose Test & Discover to list up to 128 standard interfaces. Choose Interface Controls offers Enable and Disable for each discovered interface, or you can enter a known interface index manually. Save only the controls you want exposed, then enable the connection and agent control permissions. The device must allow IF-MIB writes; discovery does not prove that permission. Disabling a management uplink may disconnect the device. Interface indexes can change after equipment reconfiguration, so review saved controls after such changes.
To monitor a physical port, use its interface operational-status OID, including that port’s interface index. Compare the result with the vendor’s documented healthy value. A device without an accessible API, SNMP, logs or an external sensor cannot report a cable being unplugged to Sysavia.
Remote scripts
Select Remote Script (SSH), choose a network agent, supply credentials and verify the equipment’s SHA256 host key fingerprint. Save a named operation containing the approved shell command, enable controls, then select it when running an action. This uses password authentication and the remote account’s permissions. It does not install an agent on that device.
For host scripts and file jobs, configure them directly under Agents. The network role does not enable arbitrary local execution.
Verify before automating
Read the live value, cause a controlled failure, and confirm that the check changes. Then create an alert. Add recovery only after the observation is reliable. Configure a fresh post-action check and a timeout failure path so an accepted restart cannot conceal a service that never returned.