Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sorting is not correct when mixing audit and error messages. #1525

Open
DCollart opened this issue Nov 21, 2024 · 1 comment
Open

Sorting is not correct when mixing audit and error messages. #1525

DCollart opened this issue Nov 21, 2024 · 1 comment

Comments

@DCollart
Copy link

DCollart commented Nov 21, 2024

Describe the bug

Description

We have some audit/error messages sorted by time sent.
The display does not respect this ordering.

Expected behavior

Either we have a way to only see error or audit messages (in that case the ordering would be OK).
Either they are still mixed together but the ordering is correct.

Actual behavior

The first page displayed a bunch of audit messages (sorted correctly) then a bunch of error messages (sorted correctly) but in the second page I see audit messages that happened after than the error messages. So they should have been displayed on the first page instead of error messages.
image

In the second page:
image

Versions

ServiceInsight : 2.13.1
ServiceControl: Empty in the about section
Please list the version of the relevant packages or applications in which the bug exists.

Steps to reproduce

Send some messages that will end up in failure.
Send some messages that will end up in audit (same endpoint). Enough to have more that one page.
Order by time sent.
In the first page you'll see some of your audit messages then the error messages.
Normally the audit messages should have filled the full first page since they have been sent later.

Check the second page and you'll see the following audit messages (expected in first page).

Relevant log output

No response

Additional Information

Workarounds

Possible solutions

Additional information

@boblangley
Copy link
Member

@DCollart We have added this bug to our priority backlog. There is no ETA for when we will get to this bug. We will update this issue when work begins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants