Local Dashboard

The feature is only available for Groundplex nodes. The user needs to have direct network access to the Groundplex node for using this functionality. Access through a HTTP load balancer is not supported.

If the Control Plane is down, you can view Ultra pipelines configured on a Groundplex through a standalone UI which receives data from the JCCs. You access this dashboard from the Secure URI for a Groundplex node, available in the Additional Information on a node in the Snaplex Health Dashboard.

For a Groundplex running on myhost.mydomain.com

  • HTTP URL would be http://myhost.mydomain.com:8090
  • HTTPS URL would be https://myhost.mydomain.com:8081 for regular Groundplex nodes and https://myhost.mydomain.com:8084 for FeedMasters.

with default values for the port numbers.

The HTTP port is accessible only if the "HTTP interface" property is set to "Any interface (", see Updating a Snaplex.

The HTTPS ports run with a self-signed TLS (SSL) certificate by default; see TLS (SSL) Certificates to find how to update the certificate.

The local admin dashboard is accessible for org admins of the organization and to members of the local_admins group. Users of "admins" and "local_admins" group will be combined to make the members of local dashboard admin group. The admin group information is cached locally on the Groundplex: updates to the group information in the control plane will take up to one hour to reflect on the Groundplex.

  • SSO login is not supported; a SnapLogic user account has to be used to login to the local dashboard. 
  • Local Dashboard can be accessed even if UI access is disabled for the user account. 
  • If the SnapLogic user's password is expired, the user cannot access the local dashboard.
  • It can take up to 10 minutes after the JCCs start (or restart) before users can log in to the local dashboard.

Users have to type in username/password to login into each node, the login session is not valid across nodes. The login session is valid for an hour.

If looking at a standard JCC node, you can see:

  • A list of running pipelines, with a subset of runinfo dialogs for each pipeline.
  • Alerts
  • Current Additional info
  • Links to connected neighbor nodes, and their state.

If looking at a Feedmaster node, you can see:

  • Tasks and queues
  • Current Additional info
  • Links to connected neighbor nodes, and their state.

If a node is disconnected from the control plane, node status, alerts, and connected neighbor node information are from the last successful heartbeat, which might not reflect real-time information. You can see a last successful heartbeat in the right top corner of the local dashboard.

See Also