Updates and Status
UTMStack v12 agents update themselves, and you can check their health both on the host and in UTMStack. This page explains how agent updates work, how to pause them, and where to look when an agent stops reporting.
How agents update
Each agent installs a second service, UTMStackUpdater, next to the agent service UTMStackAgent.
Every 5 minutes, the updater asks your UTMStack server which agent version it offers.
When the server offers a new version, the updater downloads it from the server on port 443 and verifies the download.
It replaces the agent with the new version. If the new version fails, it rolls back to the previous one.
Agents update when the agent version offered by the UTMStack server changes, which happens when your UTMStack server is updated to a release with a new agent.
The UTMStack Forwarder and the IBM AS/400 Collector do not update themselves. See UTMStack Forwarder and IBM AS/400 (IBM i) Collector.
Pause or resume updates on a host
Use the agent's set-auto-update command with administrator rights. See Agent Command Line for where the agent program is.
sudo /opt/utmstack-linux-agent/utmstack_agent_service_linux_amd64 set-auto-update off
sudo systemctl restart UTMStackUpdateroffpauses updates. The updater keeps checking but does not install what the server offers, so the agent stays on the version it has now.onresumes updates.The change takes effect the next time the updater service starts, so restart
UTMStackUpdater(or the host) after you run the command.
Pausing is not the same as choosing a version. There is no way to install an older agent version: you can only stay on the version that is already installed.
Check an agent in UTMStack
The Data Sources page (Configure > Data Sources, tab Agents): each agent shows Live (seen in the last 15 minutes), Idle (seen in the last 24 hours) or Offline (not seen for more than 24 hours, or never). Open an agent to see its events in the last 24 hours, its ingestion trend and a "possible log gap" warning when it is offline. See Data Sources Page.
Agents dashboard: shows agent activity across Linux, Windows and macOS.
Log Explorer: search the agent's data type (
wineventlog,linuxormacos) to see its latest events.
A newly installed agent appears on the Data Sources page within about a minute of starting.
Check an agent on the host
If an agent shows Idle or Offline, check it on the host.
- 1
Check that the services run
Make sure
UTMStackAgentandUTMStackUpdaterare running: in Services on Windows, withsystemctl status UTMStackAgenton Linux, or withsudo launchctl list | grep UTMStackon macOS. - 2
Check log collection
Run the agent's
statuscommand. It shows, for each log source on the host, how many events were received and saved, how many failed, and when the last event arrived. See Agent Command Line. - 3
Read the agent log
Open
logs/utmstack_agent.login the agent folder (for example/opt/utmstack-linux-agent/logs/utmstack_agent.logorC:\Program Files\UTMStack\UTMStack Agent\logs\\utmstack_agent.log). - 4
Check the network
Make sure the host still reaches your UTMStack server on 443/TCP. See Ports and Network Requirements.
While the connection is down, the agent keeps undelivered logs in its local store and sends them when the connection is back, within the limits described in Agent Command Line.
For error messages and their fixes, see Agent Troubleshooting.
How status is measured
| Signal | How often | Used for |
|---|---|---|
| Agent ping to the server | Every 15 seconds | The server counts an agent as disconnected after about a minute without a ping. |
| Agent heartbeat | Every 30 seconds | Keeps the command channel open for remote commands. |
| Host details (name, addresses, operating system) | Every 5 minutes | The Metadata shown on the Data Sources page. |
| Data Sources update | Every 60 seconds | The server copies each agent's last contact time to the Data Sources page, which shows Live, Idle or Offline from it. |
An agent can be Live while one of its sources sends nothing, for example when auditing is off on a Linux host. Check the agent's status output and its events in Log Explorer as well.