feat: PC-20078 show createdAt in replay list - #520
Merged
Conversation
The replay list endpoint sends createdAt for each item; surface it in the sloctl output. The server never sent queueTime or totalTime, so those fields are not part of the response contract.
bdw-nobl9
changed the title
bdw-nobl9
changed the title
matkaras
approved these changes
Jul 24, 2026
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
3 participants
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.
Motivation
sloctl replay listdrops thecreatedAtfield that the replay list endpoint returns for each item, because the response struct has no matching field.Summary
Added a
CreatedAtfield toReplayListItemsocreatedAtis decoded from the endpoint response and appears in table, JSON, and YAML output.Testing
sloctl replay list -o jsonagainst a live environment now includescreatedAton every row.elapsedTimeis present for in-progress replays and absent while queued (both unchanged by this PR):[ { "slo": "payments-latency", "project": "reliability-demo", "createdAt": "2026-07-24T09:33:01Z", "elapsedTime": "1h47m0s", "retrievedScope": "34 Day", "retrievedFrom": "2026-06-19T23:55:01Z", "status": "in progress", "cancellation": "possible" }, { "slo": "search-latency", "project": "reliability-demo", "createdAt": "2026-07-24T11:20:09Z", "retrievedScope": "34 Day", "retrievedFrom": "2026-06-19T23:55:09Z", "status": "queued", "cancellation": "blocked" } ]Release Notes
sloctl replay listnow showscreatedAtfor each replay.elapsedTimereflects the value returned by the API; with the accompanying server change it measures only the real process time, excluding time spent waiting in the queue, so replay list matches the web UI.