NPM report writer via the web interface

As this is on the horizon for development, I would like to add a request that there would be a way for when a Resource is added to a View at the Node or Interface level, that Report Writer - Report from Orion Report Writer had an option to flag the query to be applicable to only the Node or Interface being looked at....

In other words, a nice and neat way to implement NetObject=I:${InterfaceID} or NetObject=N:${NodeID} into the function.  In an Enterprise environment (We already know that the default reports available in Report Writer have horrible scalability for companies with large amounts of network space to monitor) using the default reports which basically search the entirety of the network in NPM and then seemingly applies the filtering after the fact is a huge load on the system as a whole.  By being able to view Node and Interface detail reports that allow (as an example) generic SUM value totals of total bytes transferred and query based on the Node or Interface being viewed would allow for some very good bandwidth reporting without risk of giving the database a huge performance hit.  Currently I see no way to tie Report Writer to SWQL filters because the query is done strictly at a SQL level.  Filters like NetObject=I:${InterfaceID} or NetObject=N:${NodeID} just fail to work.

I have been able to tie SWQL filters to other queries (mainly those that are functions built into the system which I already said do not scale very well to Enterprise customers), and have actually been able to speed up my overall NPM performance dramatically!  The more that I customize NPM and sway from anything that is prebuilt into the reporting, the better overall results I get period.

If you guys are bothering to convert the Report Writer functions into a new web based platform, please keep in mind the usefulness of being able to associate reports to Nodes and Interfaces that are specifically being researched upon.  There is no sense for a Network Wide Summary report action to take place whenever I'm trying to capture very specific Node/Interface detailed information.  Network Wide and Summary reports and resources will TANK a NPM engine that is running tens of thousands of Nodes on it.

For purposes of SolarWinds taking this into serious consideration, I request that the community feedback, support and upvote my comment vigorously.

Thank you Thwack Community for your support!

As this is on the horizon for development, I would like to add a request that there would be a way for when a Resource is added to a View at the Node or Interface level, that Report Writer - Report from Orion Report Writer had an option to flag the query to be applicable to only the Node or Interface being looked at....

In other words, a nice and neat way to implement NetObject=I:${InterfaceID} or NetObject=N:${NodeID} into the function.  In an Enterprise environment (We already know that the default reports available in Report Writer have horrible scalability for companies with large amounts of network space to monitor) using the default reports which basically search the entirety of the network in NPM and then seemingly applies the filtering after the fact is a huge load on the system as a whole.  By being able to view Node and Interface detail reports that allow (as an example) generic SUM value totals of total bytes transferred and query based on the Node or Interface being viewed would allow for some very good bandwidth reporting without risk of giving the database a huge performance hit.  Currently I see no way to tie Report Writer to SWQL filters because the query is done strictly at a SQL level.  Filters like NetObject=I:${InterfaceID} or NetObject=N:${NodeID} just fail to work.

I have been able to tie SWQL filters to other queries (mainly those that are functions built into the system which I already said do not scale very well to Enterprise customers), and have actually been able to speed up my overall NPM performance dramatically!  The more that I customize NPM and sway from anything that is prebuilt into the reporting, the better overall results I get period.

If you guys are bothering to convert the Report Writer functions into a new web based platform, please keep in mind the usefulness of being able to associate reports to Nodes and Interfaces that are specifically being researched upon.  There is no sense for a Network Wide Summary report action to take place whenever I'm trying to capture very specific Node/Interface detailed information.  Network Wide and Summary reports and resources will TANK a NPM engine that is running tens of thousands of Nodes on it.

For purposes of SolarWinds taking this into serious consideration, I request that the community feedback, support and upvote my comment vigorously.

Thank you Thwack Community for your support!