Monitoring of custom resources

Monitor and track IBM® Sterling Intelligent Promising installation by verifying the progress of custom resources and deployment pods.

Procedure

  • Steps to monitor status of custom resources and deployment pods

    The following steps demonstrate status monitoring in Red Hat® OpenShift® Container Platform. If you are using another Kubernetes platform, use the steps according to the specifics of your chosen platform.

    1. From the context selector in the navigation menu, click Operators > Installed Operators. A page that lists all the installed Operators opens.
    2. Search for the IBM Sterling Intelligent Promising Operator and click the Operator link to view details.
    3. In the Operator details page, go to the SIPEnvironment tab. If you created service groups for Inventory, Promising, and Utility services outside of SIPEnvironment, then go to the tabs of IVServiceGroup, PromisingServiceGroup, UtilityServiceGroup, OptimizerServiceGroup as required.
    4. Click the custom resource that you created.
    5. Go to the Details tab, and see the Conditions section to view the status. Alternatively, go to the YAML tab, and then verify the status that is displayed at the end of the YAML file.
    Output:
    • The progress of the custom resources is displayed including details such as, the status, last updated, reason, and message.
    • If the status message is SIPEnvironment is ready and the reason is ExecutionCompleted, the IBM Sterling Intelligent Promising is installed successfully.
    • The status message for Inventory, Promising, Utility, and Optimization service is <ServiceGroup> is ready, where <ServiceGroup> is IVServiceGroup, PromisingServiceGroup, UtilityServiceGroup, OptimizerServiceGroup.

    For more information about the status types, see Status types for IBM Sterling Intelligent Promising Operator custom resources.

  • Steps to track spec and status field changes made by the Operator and user.
    1. Familiarize yourself with the information about the built-in feature of Operator to track changes made to custom resources. For more information, see Change tracking for custom resource updates.
    2. Run the following command to access logs for Kubernetes. For others, use the appropriate command for your chosen platform. 
      kubectl logs <controller-pod-name> -n <namespace>
      Specify the <controller-pod-name> from the following two controller pods which run in the instance, one for IBM Sterling Intelligent Promising and the other for OMSGateway.
      sip-controller-manager pod
      This pod checks for Sterling Intelligent Promising and other service group changes.
      omsgateway-controller-manager pod
      This pod checks for OMSGateway and certificate manager changes.