(so a few of these issues should already be fixed)
We talked with the team today on how to best implement this.lweidig wrote: ↑Tue May 01, 2018 3:50 pmOne enhancement that would be AWESOME is if when you select devices that you could pick NetXMS container names and then it would maintain that list of devices that this applies to based on that. Would just help to provide us with more reliable automation as the containers we use / import would insure that all devices are there and over time we do not miss any or leave ones that are not valid any longer.
(since this needs to work not just for NetXMS, but also for Zabbix, and other future importers we want to add)
We decided on this:
- Importer will be able to Tag devices (using already present Tag features) that they import
like with the NetXMS importer, it would tag devices per container they were imported from.
for Zabbix, it would tag from Device Groups in Zabbix, etc.
- you will be able to run a Mass Config Push on a Tag
so setting up a confg push preset to work on a Tag would push it to all devices in the tag
- since Tags will automatically be updated by importers, this should do what you outlined
Would this be acceptable?
Will do.lweidig wrote: ↑Tue May 01, 2018 3:50 pmHow about widening the command entry window as well from the web site. Much easier to visualize if there is not so much wrapping taking place. Likely most people these days have pretty decent resolution displays for this stuff and not the sort of thing you are likely (though I am sure some will) do mobile.
We didn't include scheduling functionality with Config Push because after discussing it, we agreed that most users will just want to push on-demand.
If you have some use-cases where a scheduled push would be wanted, we would be glad to hear them
Agreed, will create a new "Automation" forum section.
Done, now present in the Beta3.
We think we found the bug, should be fixed in Beta3.
I think these 2 features should solve that:lweidig wrote: ↑Wed May 02, 2018 3:53 pmHowever, this brings me to another feature suggestion for this and that is the ability for Run Now to run against only failed / skipped devices via some sort of option. This was you can run the job multiple times without updating the working units over and over since this may cause a failure as it would here since the host is already added for the package source.
1) implement a right-click menu on output groups (including error groups)
2) in the right-click menu, add 2 options:
- rerun on these devices
- set these devices as Config Push target (would over-write currently selected devices)
Do you think that would be good enough?