Codeunit 8708 "Telemetry Loggers"

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

Properties

Events published

• OnRegisterTelemetryLogger() (integration): Allows 3d party extensions to register their own telemetry loggers to be used with Telemetry codeunit. Is used in conjunction with .
  • subscribers: Codeunit 8713 “System Telemetry Logger” OnRegisterTelemetryLogger

Procedures

• Register(TelemetryLogger: Interface "Telemetry Logger"): Registers a telemetry logger from a 3d party extension. Is used in conjunction with
• GetTelemetryLogger(Publisher: Text; var TelemetryLogger: Interface "Telemetry Logger"): Boolean + BC25 − BC25 (internal): Get the telemetry logger from publisher. If there are multiple telemetry loggers registered for the current publisher, a warning is logged.
• GetRelevantTelemetryLoggers(ExcludePublisher: Text): List of [Interface "Telemetry Logger"] + BC25 (internal): Gets the relevant telemetry loggers based on the CallerCallStack, doesn’t include the ExcludePublisher’s logger.
• SetCallStackPublishers(Publishers: List of [Text]) + BC25 (internal)
• Register(TelemetryLogger: Interface "Telemetry Logger"; Publisher: Text) (internal)

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 8709 “Telemetry Loggers Impl.” (4 calls: GetRelevantTelemetryLoggers → GetRelevantTelemetryLoggers, GetTelemetryLogger → GetTelemetryLogger, Register → Register, …)

Called by

• Codeunit 8712 “Telemetry Impl.” (4 calls: LogMessageInternal → GetRelevantTelemetryLoggers, LogMessageInternal → GetTelemetryLogger, LogMessageInternal → OnRegisterTelemetryLogger, …)
• Codeunit 8713 “System Telemetry Logger” (1 call: OnRegisterTelemetryLogger → Register)

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 Loggers"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.