Update agents
Bring one or all of your agents to the latest version from the platform; the agent rolls back on its own only if the new version fails.
When there is a new agent version, the list shows it with an arrow and the version number next to the installed version. You can update from ARGUNIS without logging in to the server.
Before you begin
You need Administer in Agents (Administrator role or a company role with that level).
The agent must be connected.
Update all
Go to Settings → Monitoring → Agents.
Click Update all to (with the version and the number of outdated agents).
Review the list of agents and confirm with Update all.
Update one
In the agent's row, click the update icon and confirm with Update.
Or open the agent's page, click Update, choose the Version and click Update.
What happens next
Each agent downloads the new version, verifies its signature and restarts. If the new version fails, it rolls back to the previous one on its own. The Installation column shows the new version when the agent reports again.
The agent's Node.js
The agent runs on its own Node.js, installed in its folder (Linux: /opt/argunis-agent/versions/<versión>/runtime; Windows: C:\Program Files\ARGUNIS\Agent\versions\<versión>\runtime). When a new agent version ships a different Node.js (for example, because of a security advisory), the update replaces it along with the agent.
It doesn't touch your server's Node.js: if your host already has
nodeinstalled for your applications, it stays the same. The agent's Node.js is not added to the PATH and doesn't replace any other.The host needs outbound access to
https://nodejs.org(or through the proxy configured in the agent) to download it. If it doesn't have it, the agent stays on the previous version and the web shows the update error.If the new version doesn't start, the agent rolls back to the previous one on its own, with its Node.js.