Global

Defines the supported KDC latency measurement contexts. Each context specifies the latency metrics applicable to a particular stage of Agent communication. The ordering of metrics determines their positions in LatencyRecord start and stop timelines. Context names and metric ordering must remain consistent with KDC-Java for cross-language interoperability.

Defines the latency metrics used by KDC to identify stages of Agent and Reply processing. These constants provide consistent metric names across KDC-Java and KDC-JS. Metrics describe the following operations: Agent processing: - AGENT_SERIALIZE: Agent serialization - AGENT_SEND: Agent transmission - AGENT_RECEIVE: Agent reception - AGENT_DESERIALIZE: Agent deserialization - AGENT_QUEUE: Time spent waiting in the Agent queue - AGENT_VISIT: Agent execution through its API Reply processing: - REPLY_WAIT: Time spent waiting for a Reply - REPLY_RECEIVE: Reply reception - REPLY_DESERIALIZE: Reply deserialization - REPLY_SERIALIZE: Reply serialization - REPLY_SEND: Reply transmission The object is frozen to prevent modification of metric definitions at runtime. These constants identify metric types; their presence does not imply that every metric is currently measured by KDC-JS.

Asynchronous Agent receiving context. Measures Agent reception, deserialization, queue processing, and visitor execution.

Synchronous Agent receiving context. Measures Agent reception and processing, followed by Reply serialization and transmission.

Asynchronous Agent sending context. Measures Agent serialization and transmission.

Synchronous Agent sending context. Includes sending-side measurements, receiving-side Agent processing measurements returned with the Reply, and synchronous reply-wait/receive measurements.