You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing ServiceControl events via ServicePulse either from dashboard (last 10 events) or via Events tab (all events - paged) the returned results are incorrectly showing oldest first rather than most recent first.
Expected behavior
Dashboard should show most recent 10 events
Events tab should show most recent first (page 1)
Actual behavior
Dashboard shows the oldest retained events (14 day retention) so need to drill down into events tab to see recent events.
Events tab also in reverse order, so we have to go to last page to see most recent events.
Note also there is another bug that means that last page also includes some old events, adding a further impedence to viewing recent events - see:
soujay
changed the title
Fetching events - last 10 or paged - now returns oldest events first.
Incorrect ordering of events in Dashboard and Events page
Jan 22, 2024
Describe the bug
Description
When viewing ServiceControl events via ServicePulse either from dashboard (last 10 events) or via Events tab (all events - paged) the returned results are incorrectly showing oldest first rather than most recent first.
Expected behavior
Actual behavior
Dashboard shows the oldest retained events (14 day retention) so need to drill down into events tab to see recent events.
Events tab also in reverse order, so we have to go to last page to see most recent events.
Note also there is another bug that means that last page also includes some old events, adding a further impedence to viewing recent events - see:
This appears to have been introduced when upgrading Service Control instance to v5 - currently on v5.0.3
Steps to reproduce
Open ServicePulse to dashboard and see most recent events are old.
Relevant log output
No response
Additional Information
Workarounds
Possible solutions
Additional information
The text was updated successfully, but these errors were encountered: