DeepakGargMsft, the ability to export the data of “.show queries”, “.show commands” to Log Analytics will be available in the following weeks. We will publish an article when it is available.
We are also working on new built-in monitoring experiences, including:
- Resource Health integration - 'Resource Health' determines the health of your Azure Data Explorer resource by examining various health status checks such as resource availability, query failures, low ingestion success rate and high update policy failures rate.
- Azure Advisor (in preview for internal MS users) - Analyzes your configurations and usage telemetry and offers personalized, actionable recommendations to help you optimize your Azure resources (including Azure Data Explorer) and help you improve availability and performance, achieve operational excellence, and reduce costs.
- Our preview recommendations include a recommendation to change machine SKU or instance count (based on parameters like data capacity and CPU utilization). Another recommendation is to consider deleting or suspending empty or unused clusters. We are now working on a new cache optimization recommendations.
- For troubleshooting, you can use the 'Diagnose and solve problems' blade. Currently, you can see manual troubleshooting steps for Kusto queries time-out. We are working on adding more troubleshooting capabilities to this blade.
- Geneva/Jarvis and Azure Support Center are MS-internal tools. You can use Geneva to monitor your cluster. Soon, we will integrate with Azure Support Center as well. This tool will provide dynamic troubleshooting insights and diagnostic tools.
Thanks,
Guy Reginiano
Azure Data Explorer (Kusto)
Microsoft