Limit size of scan payloads to prevent memory overloading
Reported by Paul Jones | 2011-07-21 15:53:04 UTC
In order to prevent a scan payload overloading the memory of the agent, it should be possible to configure a limit on the size of a scan payload that will be accepted.
If the payload is rejected, then an error message should be logged indicating that it was rejected due to size. The error should also point to documentation (perhaps via a URL in the error message) suggesting that an aggregation factor and constraint setup should be applied to reduce payload sizes. At the very least, all systems should be capable of implementing a string prefix constraint/aggregation based on their ID.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Paul Jones