bc-telemetry-generator

Instrument Business Central AL codeunits with Application Insights telemetry.

Updated May 22, 2026
One-click install
npx skills add https://github.com/javiarmesto/SampleDynamicsMinds --skill bc-telemetry-generator-javiarmesto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bc-telemetry-generator
Source: https://github.com/javiarmesto/SampleDynamicsMinds/tree/main/.agents/skills/bc-telemetry-generator
Command: npx skills add https://github.com/javiarmesto/SampleDynamicsMinds --skill bc-telemetry-generator-javiarmesto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires System Application Telemetry, Application Insights, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of adding Application Insights telemetry to Business Central AL codeunits, significantly reducing the manual effort required for observability and analytics.

Core Features & Use Cases

  • Automated Codeunit Instrumentation: Adds event, error, performance, and feature usage telemetry to codeunits.
  • Advanced Patterns: Implements best practices like event ID conventions, data classification, and common dimension use.
  • Use Case: A developer can use this Skill to automatically generate telemetry codeunits for their Business Central extensions, ensuring consistent and effective monitoring of their code.

Quick Start

Run the 'bc-telemetry-generator' skill with the path to the AL codeunit you wish to instrument.

Frequently Asked Questions about bc-telemetry-generator

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

FAQPage Schema
How do I add Application Insights telemetry to Business Central codeunits?

Automated instrumentation adds event, error, performance, and feature usage telemetry to Business Central codeunits by generating event IDs and log messages with appropriate verbosity, data classification, and scope.

What telemetry patterns should I use when instrumenting AL code?

Effective AL code instrumentation requires event ID conventions, data classification, common dimension use, and scope management to ensure consistent observability and analytics across Business Central extensions.

Do I need System Application Telemetry to instrument Business Central extensions?

Yes, instrumenting Business Central extensions with Application Insights telemetry requires the System Application Telemetry codeunit and a configured Application Insights resource to log the generated events.

How do I identify performance sensitive paths for Application Insights monitoring?

Automated telemetry generation identifies public procedures, error prone operations, and performance sensitive paths in AL codeunits, then applies appropriate verbosity and data classification to log messages.

What's the best way to automate code instrumentation for Business Central extensions?

Automated instrumentation tools generate telemetry codeunits for Business Central extensions by scanning AL code and applying monitoring best practices, significantly reducing the manual effort required for observability.

What are the limitations of automated telemetry generation for AL code?

Automated telemetry generation focuses on public procedures, error prone operations, and performance sensitive paths within AL codeunits, and its effectiveness depends on proper System Application Telemetry and Application Insights configuration.