Currently for large routing table monitoring needs the requirement is to manually edit npm.settings.json which is nonpersistent and will need to be redone upon patching Orion.
Far simpler would be to have the NPM settings provide a web based option to adjust the max without requiring an orion service restart nor will it require a manual edit of all polling engines each time patching is done.
Referencing this KB article: https://support.solarwinds.com/SuccessCenter/s/article/Fix-routing-table-resources-with-incomplete-data?language=en_US
