Skip to main content

Monitoring Deployments

Monitoring provides you a valuable insight into deployed package performance and indentify opportunties for improvement. The feature gives you visibility of FQDNs, and URLs are all up to date and functioning efficiently.

Deployment status

To view the deployment status, click on the View details on the Deployed Package details page. It will lead you to the Deployment details page where you can view the following:

  • Deployment status: Deployment being transient, it represents the initialisation of a Package configuration according to its Plan. A _Deployment_exists in a number of statuses:

  1. Planned: Orchestrator has produced a Plan for the Package Deployment. No attempt has been made to instantiate.
  2. Synchronising: OGC has requested initialisation (possibly re-initialisation in the case of a Re-Planning event) of the Package on the target Cluster. Initialisation is in progress.
  3. Running Initialisation is complete, the Deployment is running normally.
  4. Restarting:: The Deployment is stopping all services after a recoverable failure or Re-Planning event. Once services are stopped and cleared the status will move to Synchronising.
  5. Failed: One or more unrecoverable error conditions have caused the Launch to either fail to start entirely or to fail whilst active.
  6. Stopping: User has requested that the Running or Failed Deployment is deactivated and shut down. Shut down of all still-running services/resources is in progress.
  7. Stopped: All activity in Deployment has been stopped and all services and resources de-provisioned. This Deployment is now effectively out-of-scope and a new launch of the Package will result in a new Deployment.

  • Workloads Count & Status: A workload on OGC encapsulates all the information concerning a deployed instance of an Application. You will see the deployed workloads out of the desired number along with the overall deployment status, one of the listed above.

Note: If an Application is configured to have multiple replicas, a single Workload models all the replicas as a single entity with each instance recorded as a related Compute Instance.

  • Application URLs: Once the Deployment transitions to Running state, the URLs are generated for the applications where routing policies were configured.
  • Workload Status: Workload status allows you to understand your running applications information. The workload may exist in one of the following statuses:

  1. Synchronising: Workload is in the process of starting/restarting but is not yet ready for use.
  2. Running: Workload is running and ready for use.
  3. Failed: Workload has either crashed or failed to start and is unavailable.
  4. Stopped: Workload has stopped running and is not available.