Node search properties
You can use the following properties to create custom search queries within the Nodes module.
Property | Format | Description |
---|---|---|
agent_version | String | The node's Agent version. |
archived_at | Timestamp | The node's archive date. |
archived_by | String | The name of the operator or auto-archive rule that archived the node. |
archived_reason | String | The node's archive reason. |
city | String | The node's city location. |
country | String | The node's country location. |
country_code | String | The country code corresponding to the node's country location. |
distro | String | The node's OS distribution name and version. |
enrolled_at | String | The node's Agent enrollment date and time. |
hardware_id | String | The node's hardware identifier. |
hostname | String | The node's hostname. |
isolated | Boolean | Indicates whether the isolate action has been executed on the node. |
reporting_mode | String | The reporting mode of the node's Agent, which determines what data it is allowed to report. |
kernel_version | String | The node's kernel version. |
last_active | String | The time since the FortiDLP Infrastructure last received a heartbeat from the Agent. The Agent sends a heartbeat to the FortiDLP Infrastructure every 15 minutes to confirm the connection. Values must be entered in epoch or RFC3339 format. |
locked | Boolean | Indicates whether the lock action has been executed on the node. |
os | String | The node's operating system. |
remote_address | String | The node's remote address. |
rollout_exempt | Boolean | The method for directing Agents to stacks when applicable routing rules are configured with the rollout parameter. |
state | String | The node's Agent state, indicating whether the Agent has been archived or not. |
uuid | String | The node's identifier assigned by the Agent. |