Get Profile Hot Path

This skill fetches the hot path call tree from an Application Insights Profiler trace using the dataplane REST API directly.

Prerequisites

• The user must be logged in to Azure CLI (az login)
• The user must provide an Application Insights app ID (GUID) and a trace location ID (the ServiceProfilerContent value from a profiler sample)

Steps

1–2. Check investigation notes and gather inputs

Follow the Standard Skill Preamble to check for existing investigation context and gather inputs.

In addition to the standard App ID, this skill requires:

• Trace location ID: The full ServiceProfilerContent string. See trace-location-id-format.md for the format specification.

If the user doesn't have a trace location ID, help them find one by querying profiler samples — see find-profiler-traces.md.

3–8. Fetch the hot path (combined pipeline)

For efficiency, use the combined pipeline script get-hotpath-pipeline.md which performs steps 3–8 in a single PowerShell block: token acquisition → metadata → trigger → poll → root tree → child node expansion. This is the preferred approach — it reduces tool calls from 5–6 down to 1–2.

User communication: The hot path pipeline may take 1–2 minutes for fresh traces (triggering analysis, polling for completion, expanding child nodes). Before starting the pipeline, inform the user that this is a multi-step process and they should expect to wait. Provide periodic status updates based on the script's output (e.g., "Analysis triggered, polling for completion...", "Expanding call tree — round 3 of 10..."). If the trace was previously analyzed, cached results return in seconds.

If you need finer control or want to debug individual steps, the granular scripts below remain available.

3. Acquire an access token

Run the script in get-access-token.md to acquire a Bearer token for the profiler dataplane. See the token freshness and session scoping guidance in that document — re-acquire the token in the same command block as each API call. This is especially critical during the polling loop in step 6, which may run for over a minute.

4. Fetch the Redis cache region

Run the script in get-metadata.md to call the profileTreeMetadata endpoint and extract the redisCacheRegion value.

5. Trigger trace analysis

Run the script in trigger-trace-analysis.md to POST to the profileTreeDefinitions endpoint. This triggers the trace analysis using the traceLocationId and redisCacheRegion.

302 redirect handling: When the analysis results already exist, the POST returns a 302 redirect. The script disables auto-redirect (-MaximumRedirection 0) and manually follows the Location header with the Authorization header preserved. If you get the profile tree back directly from the 302 path, you can skip steps 6 and 7.

6. Poll for analysis completion

If step 5 returned 202(analysis newly triggered), run the script in poll-analysis-status.md to poll the profileTreeComputeStatus endpoint until the analysis is complete. This must succeed before fetching the profile tree.

7. Fetch the root profile tree

Run the script in get-profile-tree.md to call the profileTreeDefinitions GET endpoint. This returns the root call tree with the HotPath array (node indices) and top-level Nodes.

8. Fetch child nodes to complete the hot path

The root tree usually only contains the first 1–2 levels of nodes. The remaining nodes in the HotPath are referenced by index in ChildReferences but not inline. Run the script in get-child-nodes.md iteratively to expand them.

9. Present the hot path

Once all hot path nodes are loaded, present the result using the format described in present-hotpath.md.

Response format

See present-hotpath.md for how to interpret the profile tree JSON and display the hot path as a human-readable call tree.

Troubleshooting

401 Unauthorized during polling (302 redirect)

The most common cause of 401 errors during the polling loop (step 6) is 302 redirect auth stripping. When the analysis completes, the status endpoint returns a 302 redirect to the profile tree result. PowerShell's Invoke-RestMethod automatically follows the redirect but strips the Authorization header, causing a 401 on the redirected URL.

The updated polling script in poll-analysis-status.md handles this by using Invoke-WebRequest -MaximumRedirection 0 to detect the 302 as a completion signal without following it.

If you still see persistent 401s after the script update:

1. Verify the user is logged in: az account show
2. Re-authenticate: az login
3. Ensure the correct subscription is selected: az account set --subscription <subscription-id>
4. Try acquiring the token manually and check for errors: az account get-access-token --resource "api://dataplane.diagnosticservices.azure.com"

Analysis still "Running" after polling timeout

If the profileTreeComputeStatus endpoint still returns Running after the polling loop exhausts all attempts (default: 45 attempts / ~90 seconds):

1. Wait and retry — large traces take longer to analyze. Wait 30–60 seconds, then re-acquire a fresh token and try a direct GET on the profileTreeDefinitions endpoint (step 7). If the analysis completed in the background, the GET will return the root tree directly.
2. Try a different trace — if the trace is unusually large or corrupted, try a different profiler trace from the same time window. Shorter traces analyze faster.
3. Re-trigger the analysis — POST to the profileTreeDefinitions endpoint again (step 5). If the analysis completed, you'll get a 302 redirect to the cached result.

Analysis returns "Failed"

If the profileTreeComputeStatus endpoint returns Failed:

1. Try a different trace — the trace data may be corrupted or incomplete.
2. Check the trace time window — very old traces may have expired from storage.
3. Try with showFrameworkDependencies: true — in rare cases, changing this parameter can resolve analysis failures.

Empty or minimal root tree

If the root tree has very few nodes or the hot path is unexpectedly short:

1. Expand child nodes — the root tree only includes 1–2 levels. Follow ChildReferences using get-child-nodes.md to get the full tree.
2. Check the trace duration — very short traces (< 100ms) may not have enough samples for a meaningful call tree.
3. Try with framework dependencies — set showFrameworkDependencies: true in the trigger request to include runtime frames that may reveal hidden bottlenecks.