Percentage of actual resources used to ingest data from the total resources allocated, in the capacity policy, to perform ingestion. When a cluster isn't performing well, check the maximum value of the CPU to determine if there are specific CPUs that are blocked. The maximum value of CPU is 100%, which means there are no additional compute resources to process data. Percentage of allocated compute resources currently in use by machines in the cluster.Īn average CPU of 80% or less is sustainable for a cluster. To ensure that sufficient space is available for all the hot data, the amount of hot data needs to be reduced or the cluster needs to be scaled out. More than 100% means that the cluster's disk space is not large enough to accommodate the hot data, as defined by your caching policies. Less than 100% means that the disk space assigned for hot data is not fully utilized. No action is needed, and the cluster is completely fine. 100% means that the disk space assigned to hot data is optimally utilized. Percentage of utilized disk space dedicated for hot cache in the cluster. Use the ‘Cache utilization factor’ metric instead. This metric is deprecated and presented for backward compatibility only. If cache utilization is over 100%, the size of data to be cached is larger than the total size of cache on the cluster. Alternatively, adapt the cache policy to fewer days in cache. Scaled up to a storage-optimized pricing tier or If the average cache utilization is above 80%, the cluster should be Cache is the size of SSD allocated for user activity according to the defined cache policy.Īn average cache utilization of 80% or less is a sustainable state for a cluster. Percentage of allocated cache resources currently in use by the cluster. For example, resource and ingestion use and responsiveness. The cluster metrics track the general health of the cluster. The metrics in this article have been grouped by usage type.įor an alphabetical list of Azure Monitor's metrics for Azure Data Explorers, see supported Azure Data Explorer cluster metrics. The Azure Data Explorer metrics give insight into both overall performance and use of your resources, as well as information about specific actions, such as ingestion or query. Modify these settings in the alert rule creation pane. The new alerting rule will include your target resource, metric, splitting, and filter dimensions from your chart. Set New alert rule to visualize your metrics using the set criteria.Select Pin to dashboard to add your chart configuration to the dashboards so that you can view it again.Use Add filter and Apply splitting for metrics that have dimensions.Use the time picker to change the time range (default: past 24 hours).Select + New chart to see multiple charts in one view. ![]() Select Add metric to see multiple metrics plotted in the same chart. ![]() For more information about different metrics, see supported Azure Data Explorer metrics. To create a metric chart, select Metric name and relevant Aggregation per metric.They guide you through different options in setting up and viewing your metrics. The numbers in the following image correspond to the numbered list below. ![]() The Resource and Metric Namespace pickers are pre-selected for your Azure Data Explorer cluster. In the metrics pane, select specific metrics to track, choose how to aggregate your data, and create metric charts to view on your dashboard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |