feat(core): Add high-precision performance telemetry (Latency, TPS, TTFT) to LLM events #7176
+492
−82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
Current
LLMCallEventandLLMStreamEndEventcapture token counts but lack the temporal telemetry required for production-grade agent monitoring. To optimize agentic workflows and enforce Service Level Agreements (SLAs), developers need to measure:This PR implements high-precision timing using
time.perf_counter()to provide these metrics without breaking backward compatibility.Related issue number
Closes #5790
Checks
blackandrufflinting).Technical Details
latency_ms,tokens_per_second, andttft_msoptional fields toLLMCallEventandLLMStreamEndEventinlogging.py.OpenAIChatCompletionClientandAzureAIChatCompletionClient.ttft_msby measuring the interval between request initiation and the first yielded chunk containing content or tool calls.time.perf_counter()to ensure monotonic, high-resolution measurements immune to system clock adjustments.python/packages/autogen-core/tests/test_logging_events.pyverifying both data presence and safe handling of optional fields.