Skip to main content
After the agent runs, every host in the configuration should appear on the Hosts page in the Luumen UI with its captured properties. This page walks through the verification flow you’ll use after the first run, after adding new hosts, or after changing credentials.

​
Check the Hosts page

  1. Open the Luumen UI and go to Hosts → All hosts.
  2. Confirm the count matches the number of hosts the agent should have queried.
  3. Look for hosts marked with a warning icon — these are reachable but had a partial failure.
Each row shows the host’s hostname, the group memberships, the most recent run status, and a count of properties collected.

​
Status indicators

IndicatorMeaning
Green checkLast run completed successfully and all assigned checks evaluated.
Red XOne or more compliance checks failed on the last run.
Yellow warningThe agent reached the host but couldn’t complete data collection — typically a credential, permission, or partial command failure.
No statusThe host hasn’t been queried yet, or the most recent run did not include it.
Hover the warning icon to see the error message Luumen received from the agent.

​
Inspect a single host

Click any host to open its detail view. You’ll see:
  • Captured properties — OS version, hardware data, installed packages, any application-specific properties (e.g., SAP components when the SAP integration is enabled), and any custom properties configured during white-glove setup.
  • Check results — every check assigned to this host, with pass/fail/error and a short explanation for failures.
  • Connection state — the last successful contact time and any connection errors.
If a property you expect is missing, see Missing properties.

​
Inspect the agent logs

The agent writes per-run logs to its log_dir on the Patch server (default ./log). Logs are organized by date: 
log/
  2026-05-11/
    agent.log               # summary of the run, API calls made
    checks/
      10.0.1.42.log         # per-host command output and errors
      10.0.1.43.log
To diagnose a single host, open the file under checks/[host_ip].log for the latest run date. The file contains every command the agent ran on that host and the raw response. Property names in the logs are close to but not always identical to UI labels (for example, os_version in the log corresponds to OS Version in the UI). To confirm the agent submitted the host’s data to Luumen, look in agent.log for the API call referencing that host. A successful call means the data left the Patch server.

​
When new hosts appear

A newly added host shows up on the Hosts page after the first scheduled run that includes it. If you’ve just added a host in the UI, you can either wait for the next scheduled run or trigger a manual run from the Patch server: 
./agent-executable
The agent pulls the latest host list and settings from the API, queries every host, and exits.

​
Common verification outcomes

  • All hosts green: the agent is reaching everything with the right credentials. You’re ready to start defining compliance checks.
  • Some yellow warnings: typically credential mismatches or missing service-user permissions on specific hosts. Open the warning for the error message, then see Troubleshooting.
  • All disconnected: the agent ran but did not connect to any host. This usually means missing or wrong default credentials, or every host overriding the default with bad per-host credentials. See All hosts disconnected.
  • No hosts at all: the agent did not report data to Luumen. Check agent.log for the API call, and see Agent fails to execute.