Codeunit 1352 "Telemetry Log Metrics"

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

Properties

Events published

• OnBeforeFlushMetricsToTelemetry(var SkipTelemetry: Boolean; SumOfMeasurements: Dictionary of [Text, Decimal]; NoOfMeasurements: Dictionary of [Text, Decimal]; MinMeasurements: Dictionary of [Text, Decimal]; MaxMeasurements: Dictionary of [Text, Decimal]) (integration): This event is mainly intended for test to verify that we collect the expected metrics.

Procedures

• StartMeasureTime(MeasureName: Text): Registers the start time of a process, labeled by MeasureName
• StopMeasureTime(MeasureName: Text): Stores the elapsed time for MeasureName
• LogMeasure(MeasureName: Text; AddedValue: Decimal): Stores the AddedValue for MeasureName
• FlushMetricsToTelemetry() (internal): Sends collected metrics to telemetry and clears variables

Plus 2 local procedures.

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 1350 “Telemetry Management” (1 call: SendMetricsTelemetry → FlushMetricsToTelemetry)

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