Node details panel

Each Snaplex node is a Snaplex service running on a host or VM. In the node map or list view, click a node to view its details. JCC nodes and FeedMaster nodes have a different header.

JCC node header


Node details panel

Node details include:

  • The node name and status. The green arrow icon indicates the node is active.
  • Snaplex: The parent Snaplex name. Click the name to open Snaplex details.
  • Total vCPU: The number of CPUs on the virtual machine host.
  • Java version: The version of Java running the node.
  • Snaplex version: The parent Snaplex version.
  • Total memory: The memory available on the host.
  • OS name: The OS of the host.
  • Up since: The date and time the node started.
  • JVM memory: The memory consumed by the JVM.
  • OS arch: The chip architecture of the host.
  • Last heartbeat: Nodes in a Snaplex send a heartbeat every 20 seconds to the Control Plane to indicate they're active.
  • Disc space: Total disc space on the host.
  • OS version: The host OS version.

Feedmaster nodes header

The details panel for Feedmaster nodes contains the following information:


Feedmaster node details

Node details include:

  • The node name and status. The green arrow icon indicates the node is active.
  • Snaplex: The parent Snaplex name. Click the name to open Snaplex details.
  • Total vCPU: The number of CPUs on the virtual machine host.
  • Java version: The version of Java running the node.
  • Snaplex version: The parent Snaplex version.
  • Total memory: The memory available on the host.
  • OS name: The OS of the host.
  • Up since: The date and time the node started.
  • JVM memory: The memory consumed by the JVM.
  • OS arch: The chip architecture of the host.
  • Last heartbeat: Nodes in a Snaplex send a heartbeat every 20 seconds to the Control Plane to indicate they're active.
  • Disc space: Total disc space on the host.
  • OS version: The host OS version.
  • Request storage used: The amount of disk space currently in use by the message queue. Feedmaster nodes queue requests waiting to be processed, which are stored on disk.
  • Request storage limit: The limit set for disc use by the message queue. You can set this for Groundplexes. Refer to Deploying a FeedMaster for more information.

Actions available from the header

From the header of the node details panel, you can:

  • Click the Snaplex name to open Snaplex details.
  • For self-managed Snaplexes, Org admins can click the gear icon to start, restart, or put the node in maintenance mode.

Metrics tab

The Metrics tab displays charts of CPU, disk, memory, and file descriptor utilization along with active threads and pipelines. Refer to Metrics for more information on chart data.

Associated executions tab

From the Associated executions tab:

  • Click Open in execution view to open the Execution overview page, filtered by executions for this node.
  • Search executions by string or click the Advanced search icon to filter by invocation type, status, or project.
  • Download the pipeline execution history as a .csv file.
  • Refresh the details.

In progress requests tab (FeedMaster nodes only)

FeedMaster nodes process Ultra Task pipelines. The In progress requests tab shows how many requests are currently queued for each task and the execution time:


Feedmaster node In progress requests tab

Alerts tab

The Alerts tab is empty unless an alert occurs in the selected time period. The following shows an alert when the node was unable to ping another node in the same Snaplex:


Alerts tab

Additional details tab

The Additional details tab header displays:

  • The node IP address
  • Maximum threads
  • Maxiumum file descriptors
  • The URI
  • The secure URI

The Node diagnostics table includes data useful for performance tuning and troubleshooting. For configurable node settings and RAM use, the table displays the current, recommended, minimum, and maximum values. Values outside of the recommended range show in the top table rows in red text:


Node diagnostics table