In filebeat version greater than or equal to 8.2.0, it is found that data collection for vulnerability, asset, and the plugin data stream is going in an infinite loop as pagination termination is not happening, thus the next iteration API call is not happening at all and so new data is not getting ingested.
While the same pagination termination condition (https://github.com/elastic/beats/blob/v8.2.0/x-pack/filebeat/input/httpjson/pagination.go#L153) is working as expected in Elastic stack v7.16.0 and v8.1.0 for Tenable.sc integration and data collection is working fine.
I have gone through the code and it seems like the return statement has been removed to stop the chained calls from exiting.
https://github.com/elastic/beats/blob/v8.2.0/x-pack/filebeat/input/httpjson/response.go#L145
I'm not entirely sure but maybe this could be one causing the issue.
In filebeat version greater than or equal to 8.2.0, it is found that data collection for vulnerability, asset, and the plugin data stream is going in an infinite loop as pagination termination is not happening, thus the next iteration API call is not happening at all and so new data is not getting ingested.
While the same pagination termination condition (https://github.com/elastic/beats/blob/v8.2.0/x-pack/filebeat/input/httpjson/pagination.go#L153) is working as expected in Elastic stack v7.16.0 and v8.1.0 for Tenable.sc integration and data collection is working fine.
I have gone through the code and it seems like the return statement has been removed to stop the chained calls from exiting.
https://github.com/elastic/beats/blob/v8.2.0/x-pack/filebeat/input/httpjson/response.go#L145
I'm not entirely sure but maybe this could be one causing the issue.