Open amolnater-qasource opened 1 year ago
Pinging @elastic/fleet (Team:Fleet)
@manishgupta-qasource Please review.
Secondary review for this ticket is Done
@nimarezainia Even if this is a bug, I really would like us to think about the UX above 10k agents, shall we offer a list of agent only when a given policy is selected?
@amolnater-qasource I see the policies sorted in the 1st video. Sorry maybe missing some detail, the 2nd video is not uploaded.
@nimarezainia Even if this is a bug, I really would like us to think about the UX above 10k agents, shall we offer a list of agent only when a given policy is selected?
yes we need to think about the UI for larger scale. but not sure if this issue is the issue for that. If there's a bug we should address it IMO.
Hi @nimarezainia
We have revalidated this issue on latest 8.14.0 BC1 Kibana cloud environment and found it still reproducible.
Observations:
Screen Recording:
https://github.com/elastic/kibana/assets/77374876/0d029f43-c97e-4ad5-9542-fe490c2ad34f
Build details: VERSION: 8.14.0 BC1 BUILD: 73520 COMMIT: c1513cd7e5a00eab209ba02d30cafd6945d75470
Please let us know if anything else is required from our end.
Thanks!
Kibana Build details:
Host OS and Browser version: All, All
Preconditions:
Here we are using 10k agents installed with Horde of version 8.6.0 an 8.8.2 and a few agents of 8.10.0.
Steps to reproduce:
Expected Result: Table should get sort correctly under Agents tab for 10k agents when sorting is applied to Agent policy and Version.
Screen Recording:
https://github.com/elastic/kibana/assets/77374876/c05d97d4-a29e-468b-998f-31776611e30f
https://github.com/elastic/kibana/assets/77374876/5f55b510-cd1a-4154-b87a-312bbd5a1810