![]() For example, you can view and monitor the server side latency metric, normalized request unit usage metric, etc. ![]() Metrics: This pane provides numerical metrics that are collected at regular intervals and describes some aspect of a system at a particular time. You can view your account metrics either from the Metrics pane or the Insights pane. Sign in to the Azure portal and navigate to your Azure Cosmos DB account. By default, the metric insights are collected every five minutes and are kept for seven days. This article walks through common use cases and how Azure Cosmos DB insights can be used to analyze and debug these issues. To learn how to view metrics from Azure monitor, see Monitor Azure Cosmos DB. Therefore, you need to use case-insensitive comparison when doing string comparisons on these dimension values. The dimension values for the metrics such as container name are case-insensitive. You can also view Azure Cosmos DB metrics from Azure Monitor API. The Azure portal provides an aggregated view of these metrics. If you see an occurrence of Disk pressure, urgent cleanup of the root partition, or addition of disk space, is needed.Azure Cosmos DB provides insights for throughput, storage, consistency, availability, and latency. Messages indicating occurrences of Garbage collection can be identified with the string "imageGCManager". Messages of the form shown below are an indication of Disk pressure: > cat /var/log/messages | grep DiskPressure ![]() You can check whether this is happening by examining the kubelet logs as follows: If the disk usage rises to 80%, the likelihood of triggering Garbage collection increases. In this case 80% or 193 GB of the allocated 240 GB is available. To check the disk space available on the / partition:įilesystem Size Used Avail Use% Mounted on We recommend having a minimum of 200 GB for the /var partition, or more depending on your usage pattern. If your system has closer to 100 GB allocated, you are likely to encounter such issues. The /var partition is where kubelet and all the Enterprise Search system/user data is stored. If this cleanup results in eviction of pods that you subsequently attempt to use, you will see error messages indicating that they could not be found. When the file system reaches the maximum threshold (default is 90%), garbage collection is initiated which may result in deletion of pods, containers, images, etc until the minimum threshold (default 80%) is met. While the system is in use, Kubernetes monitors disk consumption. Refer to Information Server Enterprise Search node disk usage for details of disk space usage. Prior to installation, ensure that there is enough free disk space in the root partition, especially /var. In such a case, check disk consumption of the root partition, or more importantly wherever /var is mounted. In this example, kubectl apply -f uses the kube-apiserver pod whose log contained the error: ![]() 12:58:24.583 UTC - ERROR: kubectl set image for s4i-gremlin-console-configMap.yaml failed &įrom server for: "/opt/IBM/UGinstall/selfextract.rsniZw.2018_09_27_12_40_18/upgradetools/manifests/s4i-gremlin-console-configMap.yaml": Get : unexpected EOF > kubectl apply -f s4i-gremlin-console-configMapĮrror: error when retrieving current configuration of: Note down the pods that are not running and examine their logs to determine the cause of their failure.įor example, check if pod s4i-gremlin-console-configMap.yaml is already running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |