-
Notifications
You must be signed in to change notification settings - Fork 186
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
SCA checks are not being paginated properly #4314
Comments
Proposed solutionThe data to retrieve of the Wazuh API endpoint should be the one to be displayed in the UI. |
ResearchI was implementing the proposed solution and I found a problem to display the search bar suggestions. Before the change, these suggestions are building from the fetched data, but if it now fetches only the page data, the number of suggestions will be reduced. I was checking the SCA endpoint I asked for the possibility to add the Blocked by: wazuh/wazuh#14407 |
Partial patchI will leave a partial patch of my current development that could be useful in the future. It is not completed and requires some work to fix some things that are not working. enhance-requests-performance-sca-checks-table.partial.txt Target branch: |
The API team is working on a refactor of the SCA module and its endpoints, this issue is blocked until the following issues are finished: |
I reopened the issue because some work was not done in the previous PR: #4653 |
The current implementation of the SCA checks view in the UI is not being handled properly. It is using a single API request to load all the information for all the checks, taking too long (1 to 4s depending on the number of checks), and making the UI feel unresponsive.
We can see in the following screenshot the current request without limit:
In this case, we have 27 pages of information being loaded in a single request:
We need to ensure we use proper pagination to reduce the processing time.
This issue is related to wazuh/wazuh#7354, as the problem had already been reported and investigated several times.
The text was updated successfully, but these errors were encountered: