history_log
Used on:
The administration application gives you access to the history of a containerized xUML service ( PAS 24.0 ). To access the service history, open the details page of the service and go to section History Log. | |
In the History Log section you can inspect the service history. The log shows all actions of the xUML service (creation, start, stop etc.) including setting changes. The content of the history log is read-only. | |
Use the filter field to search for a specific entry. The content of the filter field is applied to the column Action only. | |
Click Extended filter to display the extended filter options:
If a filter is applied, the extended filter changes to . Both extended filter options are loaded dynamically:
| |
In the main filter window, you can reset all selected filters. Click Reset Filter. In the filter option window, you can also reset the selection. |
kubernetes_tab
On top of the Kubernetes section, you find the information about
Click Show all to display all available labels or annotations. | |
Below this information, you can find the two tabs Pod and Networking. |
kubernetes_tab_pod
CHECK: Excerpt contains anchor link AND corresponding anchor
Tab Pod contains the sections General and Container. The information displayed in the two sections is read-only. Pod - General Section General contains common information about the Pod: If available, you can adapt the number of Pod replicas, see below. Shows the number of Pod replicas. Scaling the Number of Replicas Move the position of the slider to the desired number of replicas you want to set. Click Apply. A pop-up window opens displaying the number of replicas before and after the change. Click Scale to confirm your choice or Cancel to abort. The new number of replicas is displayed after a refresh of the browser tab. Pod - Container Section Container consists of several tabs, one tab for each container. The content of the tabs is the same for all containers and displays the container details: Shows the container limitations. If a container exceeds its memory request and the node that it runs on becomes short of memory overall, it is likely that the Pod the container belongs to will be evicted. Limitations cannot be changed by users. They are set during system deployment If the CPU limit is exceeded, the container will be throttled, the process will slow down. Visit the official Kubernetes documentation for more information: If you click the link Ports and Volumes, the container details open in a separate pop-up. Use the filter on top of each list to search for single ports or volumes.Name Version name of the Pod. Type Shows the internal type of the replication controller. Scaling Replicas Icon Color Status Green Running Orange Starting Red Not running/erroneous Additional Labels Shows additional Pod labels if set. Name Name of the container. Image Image of the container. Ports and Volumes See below. Memory and CPU Limits Requests Memory If the memory limit is exceeded, the container will run in state OutOfMemory and then be killed.
If a container exceeds its memory request and the node that it runs on becomes short of
memory overall, it is likely that the Pod the container belongs to will be
evicted. CPU If the CPU memory request exceeds the nodes (server) capacity, the P od can be stopped and stared on a different node.
kubernetes_tab_networking
Tab Networking gives you an overview on the details of the service mesh. Use the filter to search for a port name. |