Request Demo
ZENQIX Documentation
Preview

Agent connectivity and endpoint state

How ZENQIX treats heartbeat, last-seen state, inventory freshness and outbound connectivity in the endpoint record.

Heartbeat is evidence, not a promise

Online and offline state is derived from heartbeat evidence and freshness thresholds. A device that has not reported recently should not be treated as current merely because it exists in inventory.

The interface should expose last-seen time so an operator can distinguish a fresh state from stale information.

Outbound agent connectivity

  • Agents initiate routine communication toward the control plane.
  • The endpoint record remains stable beyond a hostname change.
  • Capability reporting is platform-aware and may differ by operating system or release state.
  • Preview capability does not imply that every physical platform has completed acceptance.

Troubleshooting order

  • Confirm DNS and HTTPS reachability to the approved product endpoint.
  • Confirm the agent service is running and has a valid device identity.
  • Compare last-seen time with the expected heartbeat interval.
  • Check whether a proxy, firewall or clock problem is preventing authenticated communication.
  • Do not re-enroll a device until identity and duplicate-device consequences are understood.

Use documentation to prepare the pilot.

Add any unresolved deployment or operating question to the evaluation checklist before rollout.