kusto-analyst

Diagnose Android authentication latency and error patterns using Kusto queries.

5|5|Updated Jan 18, 2019

Search Tags:#queries #diagnostics #latency #telemetry #android #correlation #kusto

Ready to run

npx skills add https://github.com/AzureAD/android-complete --skill kusto-analyst

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kusto-analyst
Source: https://github.com/AzureAD/android-complete/tree/main/.github/skills/kusto-analyst
Command: npx skills add https://github.com/AzureAD/android-complete --skill kusto-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze Android authentication telemetry to help teams quickly identify latency issues, cross-cluster correlations, and error patterns in the authentication flow.

Core Features & Use Cases

Connect to the Azure Data Explorer (Kusto) Android telemetry cluster and query android_spans and android_metrics for diagnostics.
Identify latency hotspots, error codes, and correlation IDs (e.g., between AcquireTokenInteractive and related spans) to troubleshoot authentication failures.
Support cross-cluster investigation across Android, Broker, and eSTS flows, enabling end-to-end traceability and performance optimization.

Quick Start

Query the android_spans table for the last 7 days to identify latency spikes and error patterns.

Frequently Asked Questions about kusto-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose Android authentication latency using Kusto queries?▼

Diagnose Android authentication latency by querying the android_spans table in the Kusto telemetry cluster to surface performance hotspots. You can identify latency spikes and error patterns across authentication flows over a recent time window.

What is the best way to trace eSTS correlation IDs across Android authentication spans?▼

Trace eSTS correlation IDs by querying android_spans to match related authentication spans like AcquireTokenInteractive. This enables end-to-end traceability across Android, Broker, and eSTS flows for troubleshooting failures.

Can I perform cross-cluster analysis across Broker and app components with Kusto?▼

Yes, you can perform cross-cluster investigation across Android, Broker, and eSTS flows. Kusto queries support cross-cluster analysis to achieve end-to-end traceability and performance optimization across components.

Do I need access to the Android telemetry Kusto cluster to analyze authentication errors?▼

Yes, access to the Android telemetry Kusto cluster is required. The Skill executes structured queries against the android_spans and android_metrics tables to identify error codes and latency hotspots.

How do I identify error patterns in Android authentication telemetry?▼

Identify error patterns by querying the android_metrics and android_spans tables for diagnostic data. Structured Kusto queries surface distinct error codes and correlation IDs to troubleshoot authentication failures.

What Kusto tables are available for Android telemetry diagnostics?▼

The android_spans and android_metrics tables are available for Android telemetry diagnostics. They support structured queries to investigate latency, error patterns, and cross-cluster correlations.