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
Example: In the above example, we have 800 alerts in the group, and the latest one was a few minutes ago, but it says it was 19 hours ago because it's only looking at the latest from the first batch of results.
In alert groups, when there are more than 100 alerts in an alert group, it shows only the first 100 payloads, and it's sorted by oldest first, so the newest alerts in the group do not shows up.
It also shows the "Latest " message based on the newest alert from the first batch of 100 instead of the actual most recent alert.
The text was updated successfully, but these errors were encountered:
got it, yep it's a problem, @vadimkerr I propose to return latest alerts first, it solves the issue, now we get latest alert like: const latestAlert = alerts[alerts.length - 1];
# What this PR does
Make internal API return 100 latest alerts for alert group.
## Which issue(s) this PR fixes#857
## Checklist
- [x] Tests updated
- [x] `CHANGELOG.md` updated
Example: In the above example, we have 800 alerts in the group, and the latest one was a few minutes ago, but it says it was 19 hours ago because it's only looking at the latest from the first batch of results.
In alert groups, when there are more than 100 alerts in an alert group, it shows only the first 100 payloads, and it's sorted by oldest first, so the newest alerts in the group do not shows up.
It also shows the "Latest " message based on the newest alert from the first batch of 100 instead of the actual most recent alert.
The text was updated successfully, but these errors were encountered: