The Filter Widget contains a text area, a Submit Filter button, a Remove Filter button, and this Help button. Their descriptions are:

Filter text box: The text box accepts any text input. If the beginning of one of the valid filter keywords is being typed, an auto-complete drop-down appears. Click the keyword you are searching for, and press Enter. Selecting the desired keyword and clicking Enter will complete the word (followed by the required “:”), and allow you to type in the value you wish to filter on. For example, “name:name_of_thing”. You may enter multiple filters, and all of the key-value pairs will be used to obtain the filter results. When the cursor is in this field and the Enter key is pressed, the filter is applied and the resulting records are displayed on the page.

Submit Filter: The Submit Filter button may be clicked to apply the filter that is currently in the Filter text area.

Remove Filter: This button removes all filters and displays everything that would normally be displayed on the page when no filters are applied.

By default, the column names can be searched as text input.

Below are the fields that can be searched on (by feature).

• Jobs filter
• Node Management filter
• Pending Actions filter
• Reservations filter
• Server Management filter
• Users filter
• VM Management filter

Jobs filter:

• account: The account that this job is to run under for billing purposes
• expectedstate: The expected state of the job based on scheduler action
• holds: The types of holds that are currently on the job
• group: The group the job is run under
• jobid: The unique ID of the job
• name: The user specified name of the job
• mem: The amount of memory in MB requested by the job
• nodes: Sets the number of nodes the job has requested
• procs: The number of processors the job has requested
• qos: The QoS the job is actually running under
• runpriority: The priority to start running the job
• startpriority: The effective job priority level
• startdate: The job's actual start time
• state: The job's current state
• submitdate: The date this job was submitted
• user: The user running the job
• vmusagepolicy: The requested virtual machine usage policy for the job
• wallclock: The wallclock the job requested in seconds

Node Management filter:

• access-policy: The policy set for access to this item
• alias: The alias of the node
• architecture: The architecture for this item
• disk-available: The amount of disk space available for this item
• disk-total: The total amount of disk space this item has
• disk-utilized: The amount of disk space currently being used on this item
• features: The features that pertain to this item
• hypervisor-type: The type of the hypervisor
• id: The name of the node
• ip-address: The ip address of this item
• load: The current load on the item
• memory-available: The total amount of available memory currently unutilized by item
• memory-total: The total amount of memory belonging to this item
• memory-utilized: The total amount of memory currently being used by this item
• os: The operating system of the item
• pending-actions: The pending actions of this item
• power: The power state of the item
• power-policy: The policy set for the power of the item
• priority: The priority level of the item
• processors-available: The total number of available processors
• processors-total: The total number of processors belonging to this item
• processors-utilized: The total number of processors being used by this item
• state: The current state of this item
• substate: The current substate of this item
• vlans: The vlans this item is on

Pending Actions filter:

• id: The ID of the pending action that you wish to view
• type: The type of pending actions you wish to view
• status: The state of the pending actions you wish to view
• starttime: A period of time that has a start and an end. The format for a valid value for this key is described here
• requester: The user who performed this action
• nodeid: The ID given to the node the action is being performed upon
• targetos: The operating system that is related to the Pending Action
• vmid: The ID given to the Virtual Machine to which the Pending Action is related
• migrationsource: The source node of the Virtual Machine being migrated
• migrationdestination: The destination node of the Virtual Machine being migrated
• substatus: The sub-status of the Pending Action you wish to view

Reservations filter:

• cpu: The number of processors reserved
• disk-size: The amount of disk reserved
• duration: The duration of the reservation in seconds
• end-date: The end date of the reservation
• id: The unique ID of the reservation
• label: The label of the reservation
• memory: The amount of memory reserved
• name: The name of the reservation
• owner: The owner of the reservation
• resource-group: Text describing the resources used by the reservation
• start-date: The start date of the reservation
• state: The reservation's current state

Server Management filter:

• access-policy: Relates to the ACCESS node attribute
• alias: Primary DNS alias used by the node
• architecture: Relates to the ARCH node attribute
• disk-available: The amount of disk space reported as available
• disk-total: The total amount of disk space
• disk-utilized: The amount of disk space utilized
• features: Relates to the FEATURES node attribute
• hypervisor-type: If the node is a hypervisor, the type of hypervisor technology used
• id: The name used by Moab to identify this node
• ip-address: The primary network address of the node
• load: A measure of CPU utilization
• memory-available: The amount of RAM reported as available
• memory-total: The total amount of RAM
• memory-utilized: the amount of RAM utilized
• os: The operating system currently running on the node
• power: The state of power. "On" if the node is turned on. "Off" otherwise
• power-policy: The power-saving policy currently in place. If power saving is enabled, "Power Saving", otherwise "Manual"
• priority: The priority value (as calculated by Moab's policy engine)
• processors-available: The number of CPUs available for use
• processors-total: The total number of CPUs
• processors-utilized: The number of CPU's currently in use
• state: The current operational state of the node
• substate: A secondary state showing detailed information
• vlans: A list of VLANs to which the node belongs

Users filter:

• username: The user's username
• roles: The roles associated with the user

VM Management filter:

• id: The name of the VM
• ip-address: The ip address of this VM
• os: The operating system of the VM
• power: The setting for the power of the VM
• state: The state of the VM as reported by Moab
• substate: The substate of the VM as reported by Moab
• load: The current load average reported by the VM
• disk-utilized: The amount of disk currently in use
• disk-available: The amount of disk available
• disk-total: The total or configured amount of disk
• processors-utilized: The number of processors in use
• processors-available: The number of processors still available for use on this VM
• processors-total: The total or configured number of processors
• memory-utilized: The amount of memory currently in use
• memory-available: The amount of memory available
• memory-total: The total or configured amount of disk