Table of Contents

Telemetry

Learn how to query platform logs and completion telemetry from the Management Portal.

Overview

The Telemetry page ("Analyze platform telemetry and log data.") runs Kusto Query Language (KQL) queries against the Azure Log Analytics workspace of your FoundationaLLM instance and shows the results in filterable tables. It has two tabs:

Tab Purpose
Errors Inspect recent platform exceptions across all services
Completions Trace a single completion request by its operation ID

You can also send selected log entries to an agent for analysis.

Prerequisites

  • Access to the Management Portal.
  • Permission to run telemetry queries on the FoundationaLLM.Platform/logs resource type.
  • To use Analyze, an agent you can use to analyze logs.

Open the Telemetry Page

  1. Sign in to the Management Portal.
  2. In the sidebar, select Platform > Telemetry.

Inspect Recent Errors

  1. Select the Errors tab.
  2. In Query Template, keep Most recent 50 AppExceptions (the only template on this tab) or edit the query.
  3. Select Run Query.

The default query returns the 50 most recent AppExceptions rows with time, service (AppRoleName), problem id, method, outer and innermost messages, details, operation id, and properties.

Trace a Completion

  1. Select the Completions tab.

  2. Enter the completion's operation ID in Operation ID. Users can find the operation identifier in the User Portal when the agent is configured to show it.

  3. In Query Template, select one of:

    Template Returns
    Single completion All traces, dependencies, requests, and exceptions for the operation, in time order
    Single completion (no noise) The same, without health-check and status-polling requests
    Errors and warnings only Warnings and errors, failed requests, failed dependencies, and exceptions for the operation
  4. Select Run Query. The operation ID replaces the <operation-id> placeholder in the template.

For background on how completion telemetry is correlated, see Completion Telemetry.

Edit a Query

  1. Select the pencil button (Edit query) next to Query Template.
  2. Change the KQL in the Edit Query dialog.
  3. Select Run Query to run it and close the dialog, or Close to keep editing later.
Note

On the Completions tab, if a template is selected, Run Query reapplies the template with the current operation ID. Clear or change the template selection if you want to keep a hand-edited query.

Work with Results

Results appear under Results, one table per result set, sorted by TimeGenerated (newest first) when that column exists.

  • Filter: string columns have a Filter… box. The Type, AppRoleName, SeverityLevel, OperationId, and ParentId columns have a multi-select filter.
  • Sort and resize: select a column header to sort; drag column edges to resize.
  • Long messages: Message, OuterMessage, and InnermostMessage are truncated. Select the eye icon (View full message) to see the full text.
  • JSON details: columns of type dynamic (for example Properties) show a code icon. Select it to open the value as formatted JSON.

Analyze Log Entries with an Agent

  1. In the agent picker at the top right of the page, type at least three characters and select an agent.
  2. In the results table, select one or more rows with the checkboxes.
  3. Select Analyze.

The platform creates a new conversation named Telemetry logs analysis ({date} UTC) for you with the selected agent, and starts a completion that asks the agent to identify errors, root causes, patterns, and next steps. A notification shows the conversation ID. Open the conversation in the User Portal to read the result.

Analyze is disabled until you select at least one row and an agent. Hover over the button to see the reason.

Troubleshooting

Issue Resolution
"Failed to execute the query." Check the KQL syntax in Edit Query, and confirm the Log Analytics workspace is configured for the instance.
No results returned. Check the operation ID and widen the query time range in the KQL.
Run Query is disabled The query text is empty. Select a template or write a query.
No agents appear in the picker Type at least three characters of the agent name.