Deployment Monitors

Version: 17.07

Supported Since: 17.01

IPS comes with a set of sophisticated indicators to easily monitor the state of a particular deployment. In case of an issue of a deployment operation, these debugging features can be used to find the cause and take remedial action.

Cluster Status Indicator

Using Cluster Status Indicator, users can easily monitor the health and the state of the cluster. For a cluster there could be several states.

  • Suspended: Cluster has no any running ESB

  • Deploying: ESBs within the cluster are starting

  • Running: ESBs within the cluster are running flawlessly

  • Failed: Deployment of one or more ESBs within the cluster have not deployed successfully.

To view the state of a cluster,

  • Go to the Detail page of the cluster. The top right corner contains a Cluster Status Indicator indicating the current deployment status of the cluster. Once a deployment or cluster refresh operation is invoked, this monitor will continue to update with the latest deployment status of the cluster until a success or permanent failure status is detected.

S2I workflow
Figure 1. Cluster status

Tracking Cluster Versions

IPS keeps track of the changes that are performed on the clusters so that users can easily move between the versions of the same cluster. New version for a cluster is created when the cluster is modified and redeployed. To view the versions associated to a cluster,

  • Go to Cluster Detail page, click on Versions tab (left navigation menu).

S2I workflow
Figure 2. Cluster versions

In cluster versions view, you can see currently active version of the cluster. Clicking Details will display the projects and other metadata associated to the cluster version. You can checkout any cluster version by clicking Deploy button.

If the cluster has no active version (i.e. it has just been created or is currently suspended), this view displays the latest cluster version belonging to the cluster.

If the deployment of a new cluster version failed due to a particular reason, IPS will automatically rollback the cluster to last known working cluster version. This automatic rollback behaviour can be disabled if the users does not require such behaviour.

Deployment Progress

Deploying a cluster with a set of projects is a chain of operations. To have a properly running ESB cluster, above mentioned operations should be succeeded. IPS tracks the progress of each step of the deployment and provides an instant feedback to the users. To observe to progress of a deployment,

  • Go to Cluster Detail page, click on Deployments tab (left navigation menu).

Cluster Deployments view has a progress bar (midsection) indicating the current deployment stage of the cluster.

S2I workflow
Figure 3. Deployment progress

The progress is broken into 5 stages:

  • Pods scheduled: indicates how many new pods have been created for the latest deployment of the cluster (excluding pods for previous deployments of the same cluster, which may still be in Terminating state)

  • Pods started: indicates number of pods detected in a non-failure state, i.e. pods that are possibly running successfully

  • ESB instances started: number of successfully responding ESBs in the deployment

  • Projects started: whether all expected projects have started up successfully in all instances

  • Completed: successful completion of all previous states (and hence the deployment)

This progress bar is continually updated to display the current status of the cluster, making it ideal for detecting delayed or sporadic failures in the cluster.

In this topic
In this topic
Contact Us