Service Now Event Collector - Improved the fetch events efficiency #38182
+4
−0
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.
Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status
Related Issues
fixes: link to the issue
Description
In this bug XSUP-45347 the customer couldn't fetch audit logs since their audit logs table is loaded.
To fix that we added a use of the
sysparm_no_count
parameter in the fetch query.According to this API reference -
https://www.servicenow.com/docs/bundle/vancouver-api-reference/page/integrate/inbound-rest/concept/c_TableAPI.html
The sysparm_no_count parameter:
Setting it to True improved the efficiency of the search event function.
Another reference:
https://www.servicenow.com/community/developer-forum/rest-api-the-dreaded-quot-maximum-execution-time-exceeded-quot/m-p/1706846
Must have