community postAdministration & Setupcommunity - not Microsoftreviewed - checked by Opus

Handling Business Central Telemetry like a boss: iFacto Telemetry – Pt. 3

The iFacto Telemetry app extends Business Central's built-in telemetry capabilities by adding custom events to track missing indexes, function performance, media orphans, installed apps, delegated user actions, feature management status, and retention policies. It helps administrators monitor system health and performance across multiple customers and environments.

post waldo's blog

waldo (Eric Wauters) · 2025-05-31 · 908 words · about 4 min

"You can add a start and stop to whatever method, which causes this event to signal about the method, its duration, its NoOfSqlStatements."

Key points

  • The app sends custom telemetry events daily to track database issues like missing indexes, media orphans, and retention policy status
  • Performance tracking via start/stop markers on custom methods enables comparison of execution duration and SQL statements across customers
  • Security monitoring includes delegated user changes to critical data such as vendor bank accounts
  • Dashboard visualization consolidates custom telemetry and daily telemetry data into tabs for easier analysis
  • Job queue codeunit 1350 must run daily to ensure telemetry events are triggered

Quotes

  • “You can add a start and stop to whatever method, which causes this event to signal about the method, its duration, its NoOfSqlStatements.” (Enables granular performance tracking of custom code to identify bottlenecks and compare performance across customers)
  • “Make sure your daily telemetry is running. This is especially true for OnPrem customers, but even for SaaS it’s worth to check.” (Highlights the critical need to configure job queue for regular telemetry collection to maintain visibility into system health)
  • “This app is free, and will be free for eternity.” (Establishes the app’s long-term accessibility and removes cost barriers to adoption for telemetry-driven monitoring)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

  • codeunit “1350”

Not found in BC28-30: codeunit “1350”.

Context

  • Features: Custom telemetry events, Missing index tracking, Performance monitoring, Media orphan detection, Installed apps reporting, Feature management visibility, Retention policy monitoring, Delegated user activity logging

Source: waldo’s blog, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.