It would be great to have the ability to add custom properties at the time of discovery or atleast tag the imported nodes in a way that they are grouped to add custom properties.
Yes yes please yes. I use custom properties extensively. One use is for account limitations. I have the situation where the Network team (limited to seeing devices where "Ownergroup = Network" can discover their devices, but as soon as they are discovered, they can't SEE them because ownergroup is blank.
Agree and bump!
Here could be 2 ways to achieve this.
Option 1 would be implement a Custom Property Library that a user can select when adding a device or when doing a network discovery. This could be implemented like the custom poller section when adding a device. Simply select the library you want to implement and those fields could be populated at the point of installation.
Option 2 would be to implement a scheduled job option. This would be useful when Solarwinds discovers agent initiated communication or if you have a scheduled NPM discovery job.
We created a Powershell script that does option 2 on a nightly basis. What we ended up doing was creating a standard required file on all Windows servers that's populated with all of the custom properties. In short, the PowerShell script collects that data and uploads it to Solarwinds nightly. This works for Unix, Linux and Windows only.
Put my name on the pile.Our discoveries are already set based on things that align with custom properties and being able to set them right there would simplify a LOT of work.
This would be so useful...
Would be good
Hi, would you be able to share your PS script on the Content Exchange... would be a useful thing to have available until this is implemented!
