Name: Deployment Monitoring for SAP Commerce Cloud
Uploaded: 2023-8-29
Duration: 263 s
Description: This video presents different monitoring options during the deployment process of SAP Commerce Cloud.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div>This video presents different monitoring options during the deployment process of SAP Commerce Cloud. <br></div></div></div></div></div></div>

Deployment Monitoring for SAP Commerce Cloud

Hello. In this video, I’ll show you several tools, available to monitor SAP Commerce cloud deployments. Once a deployment is triggered, the cloud portal can display live status updates of the deployment. It usually takes some time initially for the page to be loaded, as necessary Virtual Machines need to start up in the background. Afterwards, it displays the major and minor steps, involved in the deployment as well as the status of each step. If a step is completed, a checkmark appears next to it. And if any fetal error occurs, it can cause the deployment to be automatically stopped. If a deployment is involved with initialization or data migration, you can also check the data migration logs, once the data migration step is reached. To do this, click on the three dots here, select Data migration log. This will open the Cloud Logging System page, where you can see the live view of the logs, streaming related to the data migration or initialization. If the migration runs for an unexpectedly long time, you need to navigate to the last operation, in the logs and diagnose for any issues. If the initialization or migration fails, you need to check the logs, and typically look for the last errors. With that information, you can try to diagnose the issue further, find out the cause of the failure and conduct any necessary, changes before triggering another deployment. There is another option to monitor the deployment process, namely, through the Dynatrace application performance monitoring. You can open the container groups list overview, and find the container group that is responsible, for running the update or initialization. It starts with “platform-update”. You can see any events, such as “Restarts”, or “Out of memory” events at the bottom of the page. At the top, you can see the CPU and memory usages. In case of excessive resource usage causing the container, to restart, SAP will need to adjust the resources. If there’s no problem visible on the screen, then no container resource problems have been detected. In addition, you can check the database, resource usage during a deployment as well. You can go to Dashboards and click on, SAP Performance Monitoring dashboard. Scroll down to the Database Infra Usage chart. If the chart consistently stays near to the maximum, this indicates that all the available DTU resources are being used. This may be normal during an update with migration or, initialization if heavy database operations are involved. You may just need to wait for DB operations to be completed. Once the deployment has reached, the step where services are being started, the status of the pods or containers can be observed. You can go to Dashboards and choose “SAP Kubernetes Monitoring”. Scroll down to the pod & container status section, and check the status of all the pods and containers. If the deployment involves a rolling restart, there may be more than usual number of pods listed here. Optionally, you can also check the status, of all the services by going to the Cloud Portal | Services. Click view all services and check the number of replicas. If any of the instances refuse to start, there might be a problem with the code or configuration of the services. If so, you need to check the application logs for that instance. You can navigate to the dashboard of the Cloud Logging System. From here, you can add a filter to display, only the logs of a specific service. To do this, you’ll add a filter for the pod, you can provide a service name with a wild card to search for a specific service, or you can provide the exact name of the pod. When the search results are filtered related to the specific pod, you can go through the logs to check for any warnings, or errors that why the related service can’t be started. If you find any errors or warnings, you’ll need to fix them either, by changing the configuration, or if it is code related, you’ll need to fix the coding issues, create a new build and trigger, a new deployment based on the successful build. Thanks for watching!