[FIX] [Monitoring] Retrieve data of all agents #3728
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Fixed the limit of results to retrieve to 500. - This logic could be improved with select data and increase the limit of results. See the commint included in this commit
|
LGTM |
Desvelao
deleted the
fix/3717-monitoring-not-retrieve-data-all-agents
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the problem of only index data of the first
500agents in themonitoringjob.Changes
limitquery param to 500 for each request. This could be improved as described in a comment included in the PR changes but require researching.Tests
500agents check theEvolutionvisualization displays more than500as the sum of different agent statusCloses #3717