Doesn't look like this is a hot topic for anyone else...
I ended up creating a method for performing these functions outside of the current Policy Reporting function - although I hope in a future release I can bring this back into the core Cirrus product.
An article showing how I am doing this is here
Sav.
I see policy reporting is getting an update in the next version - has this area of policy reports received any attention?
Even expanding the node selection criteria when creating a policy to include node interface data would be a great help (beyond just the current node attributes).
Use case:
I have a large number of branch devices, but only a subset have IPTEL function. I wish to create a policy just for devices prefixed with a common name and where the device has a particular loop-back defined.
I can do the first part already - but the second part is not available on the node selection filter.
Dave.
Hi Christine,
That would help - I'm using the comments field as a pseudo custom property today (which is already part of the selection criteria).
It means however that I still need to run external SQL routines to populate the comments (or custom properties) based upon data already available in NCM.
It would be much better (and more practical for the average user) if this was not required - and the selection criteria expanded beyond the current node data.
Dave.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.