docs: document time_of_last_update in /ping response#479
Closed
jesseturner21 wants to merge 1 commit into
Closed
Conversation
The /ping endpoint returns a time_of_last_update field (Unix timestamp) alongside the status, but this was not documented anywhere. Developers using the SDK had no way to know this field exists or what it represents. Fixes #471
Contributor
Author
|
Closing — the real fix belongs in the public AWS docs (AWSGenesisDocs), not the SDK docs. The SDK already emits the field correctly. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
time_of_last_updatefield in the/pingendpoint responsestatus+time_of_last_update) to the API reference sectionContext
The
/pingendpoint has always returned{"status": "...", "time_of_last_update": <unix_timestamp>}across all runtime protocols (main app, A2A, AG-UI), but thetime_of_last_updatefield was never documented. This caused confusion for developers integrating with the health check endpoint (#471).The code is correct — this is purely a documentation fix.
Test plan
Fixes #471