Azure Kusto Irql Graph

IRQL Graph Functions -- Query Results to Visualization

Apply the IRQL graph function family to tabular results. Given a KQL or IRQL query and the user's graph description, generate a Lift_To_Graph mapping and compose only the stored graph functions needed to visualize, fold, extract, or enrich the graph in Kusto Explorer. The source query does not need to use IRQL.

Scope and Routing

If a request mixes visualization and native graph analysis, use this skill for the lift/render portion and azure-kusto-graph for operator semantics. Do not replace graph-lift functions with a hand-built edges-first graph unless the user asks for native graph operators.

Input Contract

• Preferred input: a working KQL/IRQL query that produces tabular results, plus a natural-language description of the desired nodes, edges, labels, icons, extracts, enrichments, or folds.
• This skill is not a natural-language-to-KQL or NL-to-IRQL converter. It transforms existing query results into graph visualizations. For general NL-to-KQL or NL-to-IRQL conversion, use a dedicated query-generation skill (available separately).
• Preserve the supplied query's retrieval, joins, filters, and aggregations. Add only projections or synthetic IDs required by the graph mapping.
• A basic natural-language source request is supported only when it maps directly to one known table or IRQL Get_* selector with obvious columns and simple filters. State the assumed source, and do not invent joins, schema, or investigation logic.
• For non-trivial query construction, use a separate Kusto/IRQL query-generation skill first, then apply this skill to its output.
• If no query or output schema is available and the source is not trivial, request the KQL query or its result columns before generating a mapping.

Activation Triggers

Use this skill when the user:

• Supplies KQL/IRQL results and asks for an IRQL graph visualization or mapping
• Mentions Lift_To_Graph, Graph_Render_View, or Graph_Fold_By_Property
• Asks for icon-decorated node/edge mappings in Kusto Explorer
• Wants to fold/collapse nodes by a shared property
• Requests graph extraction or enrichment through Extract_Node_*, Enrich_Node_*, or Enrich_Graph_*

Do not activate this skill solely for graph-match, graph paths/components, persistent graphs, or generic make-graph construction; those belong to azure-kusto-graph.

Not a natural-language-to-KQL/IRQL converter. The input should generally be a working KQL or IRQL query whose results need graph visualization. Basic NL source requests work only for trivial single-table/selector cases. For general NL-to-KQL or NL-to-IRQL, use a dedicated query-generation skill (available separately).

Environment

• Cluster: https://kc7001.eastus.kusto.windows.net
• Databases: ValdyTimes, JoJosHospital (graph functions pre-deployed)
• Rendering: Kusto Explorer desktop app (make-graph visualization window)
• Tool: kusto_query (via Azure MCP Server)

Function Preflight

Lift_To_Graph and Graph_Render_View are stored functions, not built-in Kusto operators. Before generating or running a lift pipeline against a target database, check what is deployed:

.show functions
| where Name in~ ("Lift_To_Graph", "Graph_Render_View", "Graph_Fold_By_Property")
| project Name

• Lift_To_Graph and Graph_Render_View are required.
• Graph_Fold_By_Property is required only when folding is requested.
• Check any Extract_Node_*, Enrich_Node_*, or Enrich_Graph_* function before using it; omit optional enrichment when unavailable unless the user wants it deployed.
• If a required function is missing and you have permission to alter the database, ask the user for confirmation before deploying. Then use the .create-or-alter function definitions in references/DEPLOY_IRQL_FUNCTIONS.md. Run the relevant .create-or-alter block, then rerun the preflight check to confirm.
• If you do not have alter permissions, tell the user which functions are missing and point them to references/DEPLOY_IRQL_FUNCTIONS.md for manual deployment.

IRQL Graph Function Family

Lift_To_Graph(T, mappingJson)

Transforms any tabular KQL result into a unified node + edge table.

Input: Any table T + a JSON mapping string. Output: Rows with EntityType = "node" or "edge", ready for make-graph.

Graph_Render_View(T)

Takes Lift_To_Graph output, splits nodes/edges, and calls make-graph to open Kusto Explorer's graph window.

Graph_Fold_By_Property(T, NodeType, PropertyName)

Collapses nodes of a given type sharing a property value into a single node. Rewires edges automatically.

Graph Extraction and Enrichment Functions

These are additional stored functions that must already be deployed on the target database. They are not bundled in references/DEPLOY_IRQL_FUNCTIONS.md. Use .show functions to verify availability before including in a pipeline.

Mapping JSON Schema

The JSON mapping has two arrays: node_types and edges.

node_types[]

edges[]

Icon Repository

Use icons from https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/:

• IP: Public-IP-Addresses-(Classic).svg
• Host/VM: Virtual-Machine.svg
• User: Users.svg