diff --git a/data-explorer/azure-advisor.md b/data-explorer/azure-advisor.md index 00d6bcabee..25472822e9 100644 --- a/data-explorer/azure-advisor.md +++ b/data-explorer/azure-advisor.md @@ -3,7 +3,7 @@ title: Use Azure Advisor recommendations to optimize your Azure Data Explorer cl description: This article describes Azure Advisor recommendations used to optimize your Azure Data Explorer cluster ms.reviewer: lizlotor ms.topic: how-to -ms.date: 03/08/2023 +ms.date: 06/21/2026 --- # Use Azure Advisor recommendations to optimize your Azure Data Explorer cluster @@ -12,7 +12,7 @@ Azure Advisor analyzes Azure Data Explorer cluster configurations and usage tele ## Access Azure Advisor recommendations -There are two ways to access the Azure Advisor recommendations: +You can access the Azure Advisor recommendations in two ways: * View recommendations for [your cluster](#view-azure-advisor-recommendations-for-your-azure-data-explorer-cluster) * View recommendations for [all clusters in your subscription](#view-azure-advisor-recommendations-for-all-clusters-in-your-subscription) @@ -44,7 +44,7 @@ Azure Advisor offers different recommendation types. Use the relevant type to op :::image type="content" source="media/azure-advisor/select-recommendation.png" alt-text="Screenshot of the Azure Advisor interface showing a list of recommendations."::: -1. The window shows a list of clusters relevant to the recommendation. Recommendation details vary for each cluster and include the recommended action. +1. A list of clusters relevant to the recommendation appears. Recommendation details vary for each cluster and include the recommended action. :::image type="content" source="media/azure-advisor/clusters-with-recommendations.png" alt-text="Screenshot showing a list of clusters with relevant recommendations in Azure Advisor."::: @@ -53,7 +53,7 @@ Azure Advisor offers different recommendation types. Use the relevant type to op Cost, performance, reliability, and service excellence recommendations are available. > [!IMPORTANT] -> Your actual yearly savings may vary. The yearly savings presented are based on 'pay-as-you-go' prices. These potential savings don't take into account Azure Reserved Virtual Machine Instance (RIs) billing discounts. +> Your actual yearly savings might vary. The yearly savings presented are based on pay-as-you-go prices. These potential savings don't account for Azure Reserved Virtual Machine Instance (RIs) billing discounts. ### Cost recommendations @@ -68,14 +68,14 @@ Cost recommendations include: #### Unused running Azure Data Explorer cluster -A cluster is considered unused and running if it is in the running state and has neither ingested data nor run queries in the past five days. -In some cases, clusters may be [automatically stopped](auto-stop-clusters.md). In the following cases, the cluster won't automatically stop and a recommendation will be shown: +A cluster is unused and running if it's in the running state and it didn't ingest data or run queries in the past five days. +In some cases, clusters might be [automatically stopped](auto-stop-clusters.md). In the following cases, the cluster isn't automatically stopped and a recommendation is shown: * Leader clusters. For more information, see [follower databases](follower.md). * Clusters deployed in a Virtual Network. * Clusters where the [Auto-Stop setting](auto-stop-clusters.md#configure-auto-stop-while-creating-a-new-cluster) is turned off -The recommendation is to stop the cluster to reduce cost while preserving the data. If the data isn't needed, consider deleting the cluster to increase your savings. +Stop the cluster to reduce cost while preserving the data. If you don't need the data, consider deleting the cluster to increase your savings. #### Unused stopped Azure Data Explorer cluster @@ -84,30 +84,29 @@ A cluster is considered unused and stopped if it has been stopped for at least 6 The recommendation is to delete the cluster to reduce cost. > [!CAUTION] -> Stopped clusters may still contain data. Before deleting the cluster, verify that the data is no longer needed. Once the cluster is deleted, the data will no longer be accessible. +> Stopped clusters might still contain data. Before deleting the cluster, verify that you no longer need the data. After you delete the cluster, the data is no longer accessible. #### Change Data Explorer clusters to a more cost effective and better performing SKU -The recommendation **Change Data Explorer clusters to a more cost effective and better performing SKU** is for a cluster operating under a nonoptimal SKU. This updated SKU should reduce your costs and improve overall performance. We have calculated the required instance count that meets the cache requirements of your cluster, while ensuring that performance won't be negatively impacted. +The recommendation **Change Data Explorer clusters to a more cost effective and better performing SKU** is for a cluster operating under a nonoptimal SKU. This updated SKU reduces your costs and improves overall performance. It uses the required instance count that meets the cache requirements of your cluster, while ensuring that performance isn't negatively affected. -As part of the recommendation, we recommend enabling Optimized Autoscale if not yet enabled. Optimized Autoscale will perform a more in-depth analysis of the cluster's performance, and if needed, will further scale-in the cluster. This results in more cost reductions. The Optimized Autoscale recommendations include minimum and maximum instance count recommendations. The Max value is set to the recommended SKU instance count. If the cluster has plans to organically grow, it's recommended to manually increase this Max number. If Optimized Autoscale is already configured on your cluster, in some cases the recommendation may suggest increasing the Max instance count. +As part of the recommendation, enable Optimized Autoscale if not yet enabled. Optimized Autoscale performs a more in-depth analysis of the cluster's performance, and if needed, further scales in the cluster. This action results in more cost reductions. The Optimized Autoscale recommendations include minimum and maximum instance count recommendations. The max value is set to the recommended SKU instance count. If the cluster has plans to organically grow, manually increase this max number. If Optimized Autoscale is already configured on your cluster, in some cases the recommendation might suggest increasing the max instance count. -The SKU recommendation takes into account the current zones definitions of a cluster and if the cluster supports zones will only recommend target SKUs that have a minimum of two zones. Adding more compute availability zones doesn't incur extra costs. +The SKU recommendation takes into account the current zones definitions of a cluster, and if the cluster supports zones, only recommends target SKUs that have a minimum of two zones. Adding more compute availability zones doesn't incur extra costs. -The advisor SKU recommendation is updated every few hours. The recommendation checks for capacity availability of the selected SKU in the region. However, it's important to note that capacity availability is dynamic and changes over time. +The advisor SKU recommendation is updated every few hours. The recommendation checks for capacity availability of the selected SKU in the region. However, capacity availability is dynamic and changes over time. > [!NOTE] > The advisor SKU recommendation doesn't support clusters with Virtual Network or managed private endpoint configurations. #### Reduce cache for Azure Data Explorer tables -The **reduce Azure Data Explorer table cache period for cluster cost optimization** recommendation is given for a cluster that can reduce its table's [cache policy](/kusto/management/cache-policy?view=azure-data-explorer&preserve-view=true). This recommendation is based on the query look-back period during the last 30 days. To see where savings are possible, you can view the most relevant five tables per database for potential cache savings. This recommendation is only offered if the cluster can scale-in or scale-down after a cache policy change. Advisor checks if the cluster is "bounded by data," meaning the cluster has low CPU and low ingestion utilization, but because of high data capacity the cluster can't scale-in or scale-down. +The **reduce Azure Data Explorer table cache period for cluster cost optimization** recommendation is given for a cluster that can reduce its table's [cache policy](/kusto/management/cache-policy?view=azure-data-explorer&preserve-view=true). This recommendation is based on the query look-back period during the last 30 days. To see where savings are possible, you can view the most relevant five tables per database for potential cache savings. This recommendation is only offered if the cluster can scale in or scale down after a cache policy change. Advisor checks if the cluster is "bounded by data," meaning the cluster has low CPU and low ingestion utilization, but because of high data capacity the cluster can't scale in or scale down. #### Enable Optimized autoscale The recommendation **enable Optimized autoscale** is given when enabling [Optimized autoscale](manage-cluster-horizontal-scaling.md#optimized-autoscale-recommended-option) would have reduced the instance count on a cluster. This recommendation is based on usage patterns, cache utilization, ingestion utilization, and CPU. To make sure you don't exceed your planned budget, add a maximum instance count when you enable Optimized autoscale. - ### Performance recommendations The **Performance** recommendations improve the performance of your Azure Data Explorer clusters. @@ -117,9 +116,9 @@ Performance recommendations include the following: #### Update cache policy for Azure Data Explorer tables -The **review Azure Data Explorer table cache-period policy for better performance** recommendation is given for a cluster that requires a different look-back period time filter, or a larger [cache policy](/kusto/management/cache-policy?view=azure-data-explorer&preserve-view=true). This recommendation is based on the query look-back period of the last 30 days. Most queries run in the last 30 days accessed data not in the cache, which can increase the query run-time. You can view the top five tables per database that accessed out-of-cache data, ordered by querying percentage. +The **review Azure Data Explorer table cache-period policy for better performance** recommendation is given for a cluster that requires a different look-back period time filter, or a larger [cache policy](/kusto/management/cache-policy?view=azure-data-explorer&preserve-view=true). This recommendation is based on the query look-back period of the last 30 days. Most queries run in the last 30 days accessed data not in the cache, which can increase the query run time. You can view the top five tables per database that accessed out-of-cache data, ordered by querying percentage. -You may also get a performance recommendation to reduce the cache policy. This can happen if the cluster is data-bound. A cluster is data-bound if the data to be cached according to the caching policy is larger that the total size of the cluster's cache. Reducing the cache policy for data-bound clusters reduce the number of cache misses and potentially improves performance. +You might also get a performance recommendation to reduce the cache policy. This can happen if the cluster is data-bound. A cluster is data-bound if the data to be cached according to the caching policy is larger than the total size of the cluster's cache. Reducing the cache policy for data-bound clusters reduces the number of cache misses and potentially improves performance. ### Operational Excellence recommendations @@ -127,8 +126,8 @@ The **Operational Excellence** or "best practice" recommendations are recommenda #### Reduce table cache policy to match usage patterns -This recommendation focuses on updating the cache policy based on actual usage during the last month to reduce the hot cache for a table. Unlike the previous cost recommendation, this particular recommendation is applicable to clusters where the number of instances is determined by CPU and ingestion load rather than the amount of data stored in the hot cache. In such cases, changing the cache policy alone is insufficient to reduce the number of instances, further optimizations such as changing the SKU, reducing CPU load, and enabling autoscale are recommended to efficiently scale in. -This recommendation can be useful for tables where the actual query lookback based on usage patterns is lower than the configured cache policy. However, reducing the cache policy won’t directly lead to cost savings. The number of cluster instances is determined by CPU and ingestion load, irrespective of the amount of data stored in the hot cache. Therefore, removing data from the hot cache won't directly cause the cluster to scale in. +This recommendation focuses on updating the cache policy based on actual usage during the last month to reduce the hot cache for a table. Unlike the previous cost recommendation, this particular recommendation is applicable to clusters where the number of instances is determined by CPU and ingestion load rather than the amount of data stored in the hot cache. In such cases, changing the cache policy alone is insufficient to reduce the number of instances. We recommend further optimizations such as changing the SKU, reducing CPU load, and enabling autoscale to efficiently scale in. +This recommendation can be useful for tables where the actual query lookback based on usage patterns is lower than the configured cache policy. However, reducing the cache policy doesn't directly lead to cost savings. The number of cluster instances is determined by CPU and ingestion load, irrespective of the amount of data stored in the hot cache. Therefore, removing data from the hot cache won't directly cause the cluster to scale in. ### Reliability recommendations @@ -150,4 +149,4 @@ The recommendation is given to a virtual network cluster where the subnet is als ## Related content * [Manage cluster horizontal scaling (scale out) in Azure Data Explorer to accommodate changing demand](manage-cluster-horizontal-scaling.md) -* [Manage cluster vertical scaling (scale up) in Azure Data Explorer to accommodate changing demand](manage-cluster-vertical-scaling.md). +* [Manage cluster vertical scaling (scale up) in Azure Data Explorer to accommodate changing demand](manage-cluster-vertical-scaling.md) diff --git a/data-explorer/business-continuity-create-solution.md b/data-explorer/business-continuity-create-solution.md index 9486161a93..a6139850fc 100644 --- a/data-explorer/business-continuity-create-solution.md +++ b/data-explorer/business-continuity-create-solution.md @@ -1,18 +1,18 @@ --- title: Create business continuity and disaster recovery solutions with Azure Data Explorer description: This article describes how to create business continuity and disaster recovery solutions with Azure Data Explorer -ms.reviewer: herauch +ms.reviewer: ms.topic: how-to -ms.date: 01/03/2022 +ms.date: 06/21/2026 --- # Create business continuity and disaster recovery solutions with Azure Data Explorer -This article details how you can prepare for an Azure regional outage by replicating your Azure Data Explorer resources, management, and ingestion in different Azure regions. An example of data ingestion with Azure Event Hubs is given. Cost optimization is also discussed for different architecture configurations. For a more in-depth look at architecture considerations and recovery solutions, see the [business continuity overview](business-continuity-overview.md). +This article explains how to prepare for an Azure regional outage by replicating your Azure Data Explorer resources, management, and ingestion in different Azure regions. The article includes an example of data ingestion with Azure Event Hubs. It also discusses cost optimization for different architecture configurations. For a more in-depth look at architecture considerations and recovery solutions, see the [business continuity overview](business-continuity-overview.md). ## Prepare for Azure regional outage to protect your data -Azure Data Explorer doesn't support automatic protection against the outage of an entire Azure region. This disruption can happen during a natural disaster, like an earthquake. If you require a solution for a disaster recovery situation, do the following steps to ensure business continuity. In these steps, you'll replicate your clusters, management, and data ingestion in two Azure paired regions. +Azure Data Explorer doesn't support automatic protection against the outage of an entire Azure region. This disruption can happen during a natural disaster, like an earthquake. If you need a disaster recovery solution, follow these steps to ensure business continuity. In these steps, you replicate your clusters, management activities, and data ingestion in two Azure paired regions. 1. [Create two or more independent clusters](#create-multiple-independent-clusters) in two Azure paired regions. 1. [Replicate all management activities](#replicate-management-activities) such as creating new tables or managing user roles on each cluster. @@ -21,64 +21,64 @@ Azure Data Explorer doesn't support automatic protection against the outage of a ### Create multiple independent clusters Create more than one [Azure Data Explorer cluster](create-cluster-and-database.md) in more than one region. -Make sure that at least two of these clusters are created in [Azure paired regions](/azure/best-practices-availability-paired-regions). +Create at least two of these clusters in [Azure paired regions](/azure/best-practices-availability-paired-regions). -The following image shows replicas, three clusters in three different regions. +The following diagram shows three replica clusters in three different regions. -:::image type="content" source="media/business-continuity-create-solution/independent-clusters.png" alt-text="Create independent clusters."::: +:::image type="content" source="media/business-continuity-create-solution/independent-clusters.png" alt-text="Diagram that shows three independent Azure Data Explorer clusters in three Azure regions."::: ### Replicate management activities -Replicate the management activities to have the same cluster configuration in every replica. +Replicate management activities so every replica has the same cluster configuration. -1. Create on each replica the same: - * Databases: You can use the [Azure portal](create-cluster-and-database.md#create-a-database) or one of our [SDKs](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/kusto/Azure.ResourceManager.Kusto) to create a new database. +1. Create the same resources on each replica: + * Databases: Use the [Azure portal](create-cluster-and-database.md#create-a-database) or one of the [SDKs](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/kusto/Azure.ResourceManager.Kusto) to create a new database. * [Tables](/kusto/management/create-table-command?view=azure-data-explorer&preserve-view=true) * [Mappings](/kusto/management/create-ingestion-mapping-command?view=azure-data-explorer&preserve-view=true) * [Policies](/kusto/management/index?view=azure-data-explorer&preserve-view=true) 1. Manage the [authentication and authorization](/kusto/management/security-roles?view=azure-data-explorer&preserve-view=true) on each replica. - :::image type="content" source="media/business-continuity-create-solution/regional-duplicate-management.png" alt-text="Duplicate management activities."::: + :::image type="content" source="media/business-continuity-create-solution/regional-duplicate-management.png" alt-text="Diagram that shows replicated management activities across regional Azure Data Explorer clusters."::: -## Disaster recovery solution using event hub ingestion +## Disaster recovery solution using Event Hubs ingestion -Once you've completed [Prepare for Azure regional outage to protect your data](#prepare-for-azure-regional-outage-to-protect-your-data), your data and management are distributed to multiple regions. If there's an outage in one region, Azure Data Explorer will be able to use the other replicas. +After you complete [Prepare for Azure regional outage to protect your data](#prepare-for-azure-regional-outage-to-protect-your-data), Azure Data Explorer stores your data and management across multiple regions. If there's an outage in one region, Azure Data Explorer can use the other replicas. -### Set up ingestion using an event hub +### Set up ingestion by using Event Hubs To ingest data from [Azure Event Hubs](/azure/event-hubs/event-hubs-about) into each region's Azure Data Explorer cluster, first replicate your Azure Event Hubs setup in each region. Then configure each region's Azure Data Explorer replica to [ingest data from its corresponding Event Hubs](create-event-hubs-connection.md). > [!NOTE] -> Ingestion via Azure Event Hubs/IoT Hub/Storage is robust. If a cluster isn't available for a period of time, it will catch up at a later time and insert any pending messages or blobs. This process relies on [checkpointing](/azure/event-hubs/event-hubs-features#checkpointing). +> Ingestion through Azure Event Hubs, IoT Hub, or Storage is robust. If a cluster isn't available for time, it catches up later and inserts any pending messages or blobs. This process relies on [checkpointing](/azure/event-hubs/event-hubs-features#checkpointing). -:::image type="content" source="media/business-continuity-create-solution/event-hub-management-scheme.png" alt-text="Ingest via Azure Event Hubs."::: +:::image type="content" source="media/business-continuity-create-solution/event-hub-management-scheme.png" alt-text="Diagram that shows Event Hubs ingestion configured across regions for resilient data collection."::: -As shown in the diagram below, your data sources produce events to event hubs in all regions, and each Azure Data Explorer replica consumes the events. Data visualization components like Power BI, Grafana, or SDK powered WebApps can query one of the replicas. +This diagram shows that your data sources produce events to Event Hubs in all regions, and each Azure Data Explorer replica consumes those events. Data visualization components like Power BI, Grafana, or SDK-powered web apps can query one replica. -:::image type="content" source="media/business-continuity-create-solution/data-sources-visualization.png" alt-text="Data sources to data visualization."::: +:::image type="content" source="media/business-continuity-create-solution/data-sources-visualization.png" alt-text="Diagram that shows data sources sending events to regional replicas and client visualization tools querying a replica."::: ## Optimize costs -Now you're ready to optimize your replicas using some of the following methods: +Now you're ready to optimize your replicas by using some of the following methods: -* [Create an on-demand data recovery configuration](#create-an-on-demand-data-recovery-configuration) -* [Start and stop the replicas](#start-and-stop-the-replicas) -* [Implement a highly available application service](#implement-a-highly-available-application-service) -* [Optimize cost in an active-active configuration](#optimize-cost-in-an-active-active-configuration) +* [Create an on-demand data recovery configuration](#create-an-on-demand-data-recovery-configuration). +* [Start and stop the replicas](#start-and-stop-the-replicas). +* [Implement a highly available application service](#implement-a-highly-available-application-service). +* [Optimize cost in an active-active configuration](#optimize-cost-in-an-active-active-configuration). ### Create an on-demand data recovery configuration -Replicating and updating the Azure Data Explorer setup will linearly increase the cost with the number of replicas. To optimize cost, you can implement an architectural variant to balance time, failover, and cost. -In an on-demand data recovery configuration, cost optimization has been implemented by introducing passive Azure Data Explorer replicas. These replicas are only turned on if there's a disaster in the primary region (for example, region A). The replicas in Regions B and C don't need to be active 24/7, reducing the cost significantly. However, in most cases, the performance of these replicas won't be as good as the primary cluster. For more information, see [On-demand data recovery configuration](business-continuity-overview.md#on-demand-data-recovery-configuration). +Replicating and updating the Azure Data Explorer setup linearly increases cost as the number of replicas increases. To optimize cost, implement an architectural variant that balances time, failover, and cost. +An on-demand data recovery configuration optimizes cost by using passive Azure Data Explorer replicas. These replicas are only turned on if there's a disaster in the primary region (for example, region A). The replicas in Regions B and C don't need to be active 24/7, which significantly reduces the cost. But in most cases, these replicas don't perform and the primary cluster. For more information, see [On-demand data recovery configuration](business-continuity-overview.md#on-demand-data-recovery-configuration). -In the image below, only one cluster is ingesting data from the event hub. The primary cluster in Region A performs [continuous data export](/kusto/management/data-export/continuous-data-export?view=azure-data-explorer&preserve-view=true) of all data to a storage account. The secondary replicas have access to the data using [external tables](/kusto/query/schema-entities/external-tables?view=azure-data-explorer&preserve-view=true). +In the following diagram, only one cluster ingests data from Event Hubs. The primary cluster in Region A performs [continuous data export](/kusto/management/data-export/continuous-data-export?view=azure-data-explorer&preserve-view=true) of all data to a storage account. The secondary replicas access the data by using [external tables](/kusto/query/schema-entities/external-tables?view=azure-data-explorer&preserve-view=true). -:::image type="content" source="media/business-continuity-create-solution/active-hot-standby-scheme.png" alt-text="architecture for an on-demand data recovery configuration."::: +:::image type="content" source="media/business-continuity-create-solution/active-hot-standby-scheme.png" alt-text="Diagram that shows an on-demand data recovery architecture with one active primary cluster and passive replicas."::: ### Start and stop the replicas -You can start and stop the secondary replicas using one of the following methods: +Start and stop the secondary replicas by using one of the following methods: * [Azure Data Explorer connector to Power Automate (preview)](flow.md) @@ -87,7 +87,7 @@ You can start and stop the secondary replicas using one of the following methods * Azure CLI: ```azurecli -az kusto cluster stop --name= --resource-group= --subscription=" +az kusto cluster stop --name= --resource-group= --subscription= ``` ### Implement a highly available application service @@ -101,13 +101,13 @@ This section shows you how to create an [Azure App Service](https://azure.micros > [!TIP] > Having multiple connections between replicas in the same service gives you increased availability. This setup isn't only useful in instances of regional outages. -1. Use this [boilerplate code for an app service](https://github.com/Azure/azure-kusto-bcdr-boilerplate). To implement a multi-cluster client, the [AdxBcdrClient](https://github.com/Azure/azure-kusto-bcdr-boilerplate/blob/master/webapp/ADX/AdxBcdrClient.cs) class has been created. Each query that is executed using this client will be sent [first to the primary cluster](https://github.com/Azure/azure-kusto-bcdr-boilerplate/blob/26f8c092982cb8a3757761217627c0e94928ee07/webapp/ADX/AdxBcdrClient.cs#L69). If there's a failure, the query will be sent to secondary replicas. +1. Use this [boilerplate code for an app service](https://github.com/Azure/azure-kusto-bcdr-boilerplate). To implement a multicluster client, use the [AdxBcdrClient](https://github.com/Azure/azure-kusto-bcdr-boilerplate/blob/master/webapp/ADX/AdxBcdrClient.cs) class. Each query that this client executes is sent [first to the primary cluster](https://github.com/Azure/azure-kusto-bcdr-boilerplate/blob/26f8c092982cb8a3757761217627c0e94928ee07/webapp/ADX/AdxBcdrClient.cs#L69). If a failure occurs, the query is sent to secondary replicas. -1. Use [custom application insights metrics](/azure/azure-monitor/app/api-custom-events-metrics) to measure performance, and request distribution to primary and secondary clusters. +1. Use [custom application insights metrics](/azure/azure-monitor/app/api-custom-events-metrics) to measure performance and request distribution to primary and secondary clusters. #### Test the Azure App Service BCDR client -We ran a test using multiple Azure Data Explorer replicas. After a simulated outage of primary and secondary clusters, you can see that the app service BCDR client is behaving as intended. +The following test uses multiple Azure Data Explorer replicas. After a simulated outage of primary and secondary clusters, the App Service BCDR client behaves as intended. :::image type="content" source="media/business-continuity-create-solution/simulation-verify-service.png" alt-text="Verify app service BCDR client."::: @@ -120,7 +120,7 @@ The Azure Data Explorer clusters are distributed across West Europe (2xD14v2 pri #### Perform dynamic or static routing -Use [Azure Traffic Manager routing methods](/azure/traffic-manager/traffic-manager-routing-methods) for dynamic or static routing of the requests. Azure Traffic Manager is a DNS-based traffic load balancer that enables you to distribute app service traffic. This traffic is optimized to services across global Azure regions, while providing high availability and responsiveness. +Use [Azure Traffic Manager routing methods](/azure/traffic-manager/traffic-manager-routing-methods) for dynamic or static request routing. Azure Traffic Manager is a DNS-based traffic load balancer that you can use to distribute App Service traffic. This traffic is optimized to services across global Azure regions, while providing high availability and responsiveness. You can also use [Azure Front Door based routing](/azure/frontdoor/front-door-routing-methods). For comparison of these two methods, see [Load-balancing with Azure's application delivery suite](/azure/frontdoor/front-door-lb-with-azure-app-delivery-suite). @@ -130,9 +130,9 @@ Using an active-active configuration for disaster recovery increases the cost li #### Use optimized autoscale to optimize costs -Use the [optimized autoscale](manage-cluster-horizontal-scaling.md#optimized-autoscale-recommended-option) feature to configure horizontal scaling for the secondary clusters. They should be dimensioned so they can handle the ingestion load. Once the primary cluster isn't reachable, the secondary clusters will get more traffic and scale according to the configuration. +Use the [optimized autoscale](manage-cluster-horizontal-scaling.md#optimized-autoscale-recommended-option) feature to configure horizontal scaling for the secondary clusters. Size secondary clusters to handle the ingestion load. When the primary cluster isn't reachable, secondary clusters get more traffic and scale according to the configuration. -Using optimized autoscale in this example saved roughly 50% of the cost in comparison to having the same horizontal and vertical scale on all replicas. +In this example, optimized autoscale saves roughly 50% in cost compared to using the same horizontal and vertical scale on all replicas. ## Related content diff --git a/data-explorer/dashboard-troubleshoot-tile-errors.md b/data-explorer/dashboard-troubleshoot-tile-errors.md new file mode 100644 index 0000000000..8bdf146c8b --- /dev/null +++ b/data-explorer/dashboard-troubleshoot-tile-errors.md @@ -0,0 +1,113 @@ +--- +title: Troubleshoot dashboard tile errors in Azure Data Explorer +description: Learn how to troubleshoot errors in Azure Data Explorer dashboard tiles. +ms.reviewer: naor-bitton_microsoft +ms.topic: concept-article +ms.date: 06/21/2026 + +#customer intent: I want to learn how to troubleshoot errors in my dashboard tiles in Azure Data Explorer. +--- + +# Troubleshoot dashboard tile errors in Azure Data Explorer + +When you work with dashboards in Azure Data Explorer, a tile might display an error instead of a visual. These errors are categorized to help you understand the type of issue and determine next steps. +Each error type indicates a different stage in the query, data retrieval, or rendering process where the failure occurred. + +:::image type="content" source="media\troubleshoot-dashboard-tile-error\error-tiles.png" alt-text="Screenshot of different tile error types examples."::: + +## Understand tile error types + +The following section describes common tile error categories, what they mean, and general ways to address them. + +### Access denied + +The tile can't access or retrieve data from the underlying data source. This error occurs when the user lacks permission to access the data source. + +**What to do:** + +- Verify the data source exists and is reachable. +- Check that you have permission to access the data source. +- Try refreshing after confirming availability. + +### Syntax error + +The query used in the tile contains invalid syntax and can't be parsed. This error occurs after editing a query or when creating a new tile. + +**What to do:** + +- Review the query for syntax problems, such as missing operators or invalid expressions. +- Validate the query in the query editor. +- Revert recent changes if the error appeared after modification. + +### Semantic error + +The query is syntactically valid but uses invalid references or logic. This error occurs when the query refers to non-existent tables, columns, or incompatible data types. + +**What to do:** + +- Ensure referenced tables and columns exist. +- Check for renamed or deleted objects. +- Validate query logic and data types. +- Update the query to match the current schema. + +### Network error + +The connection between the dashboard and backend services failed. This error occurs due to temporary connectivity problems or service interruptions. + +**What to do:** + +- Check your network connection. +- Refresh the dashboard. +- Retry after a short time if the issue is transient. +- If the problem persists, check service health or contact support. + +### Visual formatting issue + +The tile can't render the visual due to configuration or formatting problems. This problem occurs when the query runs successfully but the visual fails to display correctly. + +**What to do:** + +- Review visual settings, such as field assignments and formatting rules. +- Ensure required fields are included. +- Simplify or reset the visual configuration. +- Recreate the visual if needed. + +### An error occurred + +A general error occurred that doesn't fit the preceding categories. This catch-all error can occur for various reasons, such as unexpected exceptions or unhandled cases. + +**What to do:** + +- Check the error message for more details. +- Review recent changes to the tile, query, or data source. +- Try refreshing the dashboard. +- If the problem persists, contact support with the error details. + +## Get more details from error messages + +When a tile error occurs, hover over the tile to expose the **Details** button. Select this button to get more information about the error, including error codes and messages that can help identify the root cause. + +For example: + +:::image type="content" source="media\troubleshoot-dashboard-tile-error\details.png" alt-text="Screenshot of tile error details example."::: + +## General troubleshooting approach + +If you're unsure how to proceed: + +- Refresh the dashboard to rule out temporary problems. +- Check other tiles: + - If multiple tiles fail, there's possibly a data source or service problem. + - If one tile fails, there's likely a query or configuration problem. +- Review recent changes: + - Query edits + - Data source updates + - Permission changes +- Validate the query in the editor where possible. +- Contact your administrator or data owner if the problem involves access or shared resources. + +## Related articles + +- [Create a dashboard in Azure Data Explorer](azure-data-explorer-dashboards.md) +- [Explore data in dashboard tiles](dashboard-explore-data.md) +- [Visualize sample data in dashboards](web-ui-samples-dashboards.md) \ No newline at end of file diff --git a/data-explorer/media/one-click-table-policies/one-click-retention-policy-start.png b/data-explorer/media/one-click-table-policies/one-click-retention-policy-start.png index 14d87ec99d..6dff8c2c69 100644 Binary files a/data-explorer/media/one-click-table-policies/one-click-retention-policy-start.png and b/data-explorer/media/one-click-table-policies/one-click-retention-policy-start.png differ diff --git a/data-explorer/media/one-click-table-policies/one-click-retention.png b/data-explorer/media/one-click-table-policies/one-click-retention.png index 98ad1b335d..85185066ec 100644 Binary files a/data-explorer/media/one-click-table-policies/one-click-retention.png and b/data-explorer/media/one-click-table-policies/one-click-retention.png differ diff --git a/data-explorer/media/troubleshoot-dashboard-tile-error/details.png b/data-explorer/media/troubleshoot-dashboard-tile-error/details.png new file mode 100644 index 0000000000..6ead0dc0fa Binary files /dev/null and b/data-explorer/media/troubleshoot-dashboard-tile-error/details.png differ diff --git a/data-explorer/media/troubleshoot-dashboard-tile-error/error-tiles.png b/data-explorer/media/troubleshoot-dashboard-tile-error/error-tiles.png new file mode 100644 index 0000000000..4e1f6640b8 Binary files /dev/null and b/data-explorer/media/troubleshoot-dashboard-tile-error/error-tiles.png differ diff --git a/data-explorer/migrate-cluster-to-multiple-availability-zone.md b/data-explorer/migrate-cluster-to-multiple-availability-zone.md index 906120046e..4a2e87f62b 100644 --- a/data-explorer/migrate-cluster-to-multiple-availability-zone.md +++ b/data-explorer/migrate-cluster-to-multiple-availability-zone.md @@ -1,33 +1,35 @@ --- -title: Migrate your cluster to support multiple availability zones (preview) -description: This guide teaches you how to migrate your cluster to support multiple availability zones. -ms.reviewer: iriskaminer -ms.date: 03/09/2025 +title: "Migrate cluster to multiple availability zones (preview)" +description: "Learn how to migrate your Azure Data Explorer cluster to support multiple availability zones for improved resiliency. Follow this step-by-step guide to get started." +ms.date: 06/14/2026 +author: spelluru +ms.author: spelluru +ms.reviewer: ms.topic: how-to --- # Migrate your cluster to support multiple availability zones (preview) -Many Azure regions provide availability zones, which are separated groups of datacenters within a region. Availability zones are close enough to have low-latency connections to other availability zones. They're connected by a high-performance network with a round-trip latency of less than 2 ms. However, availability zones are far enough apart to reduce the likelihood that more than one will be affected by local outages or weather. Availability zones have independent power, cooling, and networking infrastructure. They're designed so that if one zone experiences an outage, then regional services, capacity, and high availability are supported by the remaining zones. For more information, see [Azure Availability Zones](/azure/availability-zones/az-overview). +Many Azure regions provide availability zones, which are separated groups of datacenters within a region. Availability zones are close enough to have low-latency connections to other availability zones. They're connected by a high-performance network with a round-trip latency of less than 2 ms. However, availability zones are far enough apart to reduce the likelihood that local outages or weather affect more than one availability zone. Each availability zone has independent power, cooling, and networking infrastructure. They're designed so that if one zone experiences an outage, the remaining zones support regional services, capacity, and high availability. For more information, see [Azure Availability Zones](/azure/availability-zones/az-overview). -Azure Data Explorer clusters can be configured to use availability zones in supported regions. By using availability zones, a cluster can better withstand the failure of a single datacenter in a region to support [business continuity](business-continuity-overview.md) scenarios. +You can configure Azure Data Explorer clusters to use availability zones in supported regions. By using availability zones, a cluster can better withstand the failure of a single datacenter in a region to support [business continuity](business-continuity-overview.md) scenarios. -You can configure availability zones when creating a cluster [in the Azure portal](create-cluster-and-database.md#create-a-cluster) or [programmatically](create-cluster-database.md) using one of the following methods: +You can configure availability zones when creating a cluster [in the Azure portal](create-cluster-and-database.md#create-a-cluster) or [programmatically](create-cluster-database.md) by using one of the following methods: - REST API - C# SDK - Python SDK - PowerShell -- ARM Template +- ARM template > [!IMPORTANT] > -> - Once a cluster is configured with availability zones, you can't change the cluster to not use availability zones. -> - Multiple zones aren't supported in all regions. Therefore, clusters located in these regions can't be set up to use availability zones. -> - Using availability zones incurs additional costs for storage. +> - After you configure a cluster with availability zones, you can't change the cluster to not use availability zones. +> - Not all regions support multiple zones. Therefore, you can't set up clusters in these regions to use availability zones. +> - Using availability zones incurs extra costs for storage. > [!NOTE] > -> - Before you proceed, make sure you familiar with the [migration process and considerations](#migration-process). +> - Before you proceed, make sure you're familiar with the [Migration process and considerations](#migration-process-and-considerations). > - You can also use these steps to change the zones of an existing cluster that uses availability zones. In this article, you learn about: @@ -36,14 +38,14 @@ In this article, you learn about: > > - How to [configure your cluster to support availability zones](#configure-your-cluster-to-support-availability-zones) > - The [architecture of clusters with availability zones](#architecture-of-clusters-with-availability-zones) -> - The [migration process and considerations](#migration-process) +> - The [migration process and considerations](#migration-process-and-considerations) ## Prerequisites - Make sure your cluster is in a [region where multiple availability zones are supported](/azure/reliability/regions-list). -- For migrating a cluster to support availability zones, you need a cluster that was deployed without availability zone support. -- For changing the zones of a cluster, you need a cluster that is configured with availability zones. +- To migrate a cluster to support availability zones, you need a cluster that you deployed without availability zone support. +- To change the zones of a cluster, you need a cluster that is configured with availability zones. - For REST API, familiarize yourself with [Manage Azure resources by using the REST API](/azure/azure-resource-manager/management/manage-resources-rest). - For other programmatic methods, see [Prerequisites](create-cluster-database.md#prerequisites). @@ -57,9 +59,9 @@ You can get a list of availability zones for your cluster in the following ways: 1. Under **Settings**, select **Scale up**. -1. In the row for your cluster, the availability zones are listed in the **Availability zones** column. +1. In the row for your cluster, the availability zones appear in the **Availability zones** column. - :::image type="content" source="media/migrate-cluster-to-multiple-availability-zone/availability-zones-list.png" lightbox="media/migrate-cluster-to-multiple-availability-zone/availability-zones-list.png" alt-text="Availability zones"::: + :::image type="content" source="media/migrate-cluster-to-multiple-availability-zone/availability-zones-list.png" lightbox="media/migrate-cluster-to-multiple-availability-zone/availability-zones-list.png" alt-text="Screenshot of the Scale up page in the Azure portal showing the availability zones column with zones listed for the selected cluster.":::