Codeunit 8709 "Telemetry Loggers Impl."
System Application · System.Telemetry
Across versions
- BC23-24present
- BC253 procedures added, 2 procedures removed
- BC26-30unchanged
Neighbourhood 1 connected objects and pages
System Application · System.Telemetry · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
Register(TelemetryLogger: Interface "Telemetry Logger"; Publisher: Text)GetTelemetryLogger(Publisher: Text; var TelemetryLogger: Interface "Telemetry Logger"): Boolean+ BC25 − BC25 (internal)GetRelevantTelemetryLoggers(ExcludePublisher: Text): List of [Interface "Telemetry Logger"]+ BC25 (internal)SetCallStackPublishers(Publishers: List of [Text])+ BC25 (internal)
Called by
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 8708 “Telemetry Loggers” (4 calls:
GetRelevantTelemetryLoggers → GetRelevantTelemetryLoggers,GetTelemetryLogger → GetTelemetryLogger,Register → 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 Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.