Skip to content

Telemetry MCP

Telemetry has two parts: logging signals and retrieving them. For logging, we use Session.LogMessage with Azure Application Insights. For retrieval, we use the BC Telemetry Buddy MCP — which lets the agent query your telemetry in plain English.

How BC extension telemetry works

Session.LogMessage in AL sends signals to Azure Application Insights — but only if your extension's app.json includes a connection string. No container changes needed. The extension routes its own telemetry directly, independently of the server or container configuration.

Set up Application Insights

  1. In the Azure portal, create an Application Insights resource (free tier works).
  2. Copy the Connection String from the Overview page.
  3. Add it to app/app.json:
{
  "applicationInsightsConnectionString": "<your-connection-string>"
}
  1. Republish the extension. From that point, every Session.LogMessage call in your AL code sends a signal to your Application Insights workspace.

DataClassification matters

Only telemetry events with DataClassification = SystemMetadata are sent to Application Insights. Events with any other classification are silently dropped.

Install BC Telemetry Buddy MCP

BC Telemetry Buddy MCP lets you query your telemetry by simply asking questions in plain language. The easiest way to set it up is to ask the agent:

Please configure the bc-telemetry-buddy-mcp for me.
Reference: https://www.npmjs.com/package/bc-telemetry-buddy-mcp

The agent will install and configure it for your harness. You'll need your Application Insights App ID and Azure credentials ready.

Alternatively, follow the manual instructions at github.com/waldo1001/waldo.BCTelemetryBuddy.

Once configured, the MCP will be ready to query your telemetry after the AL signals are implemented.

Implement →