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) is the regular Snaplex service. A FeedMaster is a special service that supports streaming input by distributing Ultra Task requests to the JCC services. Learn more about Ultra Tasks

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 services also ping the control plane with a heartbeat every 20 seconds. When a service fails to contact the control plane for 15 minutes, it's considered offline.

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.

Learn more about the Infrastructure and Metrics pages:

• Monitor and manage the infrastructure describes common tasks that you can perform from the System overview page.
• System overview graph view explains how to interpret the graph view.
• System overview list view shows how to use the list view.
• Snaplex details panel and Node details panel provides more information about the details panels.
• Metrics explains the charts for a node and how to use them.