Infrastructure

Overview of Snaplexes and the System overview and Metrics pages in Monitor

Snaplex services and nodes

Snaplexes execute pipelines and can be one of the following types:

  • Cloudplex: Provisioned and managed by SnapLogic on your behalf.
  • Groundplex: Deployed and managed by your organization on a cloud or local network.
  • AutoSync Snaplex: A Cloudplex managed by SnapLogic for customers who have purchased AutoSync.

A Snaplex is usually deployed as multiple instances. Each service runs on a different physical host or virtual machine. The documentation refers to the Snaplex service and the host on which it runs as a node. The Java Component Container (JCC), also known as an execution node, is the regular Snaplex service. A FeedMaster is a special node that distributes Ultra Tasks requests to execution nodes. It queues the overflow until the execution nodes are ready to handle them.

The services in a Snaplex communicate with each other periodically and generate alerts when they detect issues. For example, a communication failure causes an Unable to reach Snaplex neighbor alert. You can view Snaplex alerts on the Monitor Alert history page or the Snaplex details Alerts tab.

Snaplex nodes ping the control plane with a heartbeat every 20 seconds. When a node fails to contact the control plane for 5 minutes, it's considered inactive.

Comparison of the System overview and Metrics pages

The System overview page displays information about the Snaplex services and the hosts on which they run. The Metrics page contains more detailed graphs for a single node. They both show information about infrastructure usage, resource consumption, and system health. The table below summarizes the differences.

Metrics page System overview page
Scope
  • Single node
  • All execution nodes
  • All FeedMaster nodes
All Snaplexes and their nodes
Type of visualization Plotted line graphs Color-coded bar graph view showing average and maximum usage and list view in table format.

Learn more about the Infrastructure and Metrics pages: