Agent FAQ

How much system resources does the Go Agent consume?

The WatchGrid Go Agent is lightweight and optimized for minimal resource impact. It typically consumes less than 15 MB RAM and negligible CPU resources (< 0.1%).

How does the agent operate without open inbound firewall ports?

The agent uses an outbound pull/push model over standard HTTPS/HTTP port 443/80. No inbound ports need to be opened on your firewall or host system.

What happens if internet connection or WatchGrid server connectivity is temporarily lost?

The agent automatically uses its local configuration cache stored at /etc/watchgrid/config.json. Once connectivity is restored, cached metrics and updates resume automatically.

How is the agent managed on Linux?

The agent runs as a native systemd service (watchgrid.service). You can inspect or restart it using standard commands: systemctl status watchgrid or systemctl restart watchgrid.