Codeunit 1350 "Telemetry Management"

Base Application · System.Telemetry · BC23-30 · source at ea08af5e · facts from BC29

Events published

• OnSendDailyTelemetry() Δ BC27 (integration)
  • subscribers: Codeunit 1351 “Telemetry Subscribers” SendDailyTelemetry, Codeunit 1392 “Monitor Sensitive Field” SendTelemetryOnActivityTelemetry

Event subscriptions

• ScheduleDailyTelemetryAfterCompanyOpen subscribes to Codeunit “System Initialization” OnAfterLogin
• SendMetricsTelemetry subscribes to Codeunit “LogInManagement” OnAfterCompanyClose

Triggers

OnRun

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 1352 “Telemetry Log Metrics” (1 call: SendMetricsTelemetry → FlushMetricsToTelemetry)
• Codeunit 453 “Job Queue - Enqueue” (1 call: ScheduleDailyTelemetryAfterCompanyOpen → (object))
• Codeunit 457 “Environment Information” (1 call: ScheduleDailyTelemetryAfterCompanyOpen → IsSaaS)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Telemetry Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.