The option to set the amount of fails before the alarm gets triggered should be adjustable for every single script check, just like the service checks.
Scripts configured for execution before oder after backup are executed before backing up every single datasource configured in that time plan/schedule. There should be an option to execute the scripts only once befor starting the backup for the first datasource and after finishing the last of the configured datasources. To achieve that behaviour is not possible right now. Sure: If a script is only needed to be executed ...more »
Could you make it possible that when a automation script has been run we can put the output of the script into the body of an e-mail without having to mail it through a self defined smtp server. Now i use the Nofication Sussess Failed and Send task output file in Email. But this is in a zipped file and i would like to have it as the Body of the mail. Maybe you can make a output to body of nofication mail in the automation ...more »
We would like to be able to configure a script for patch and reboot window, instead of creating a separate scheduled task.
The idea is to be able to run a certain shutdown script anywhere in the PM Window when required.
This would be only for PM reboot window and installation window.
I'd like the ability to block customer level users from being able to access filter/dashboard/repositoy items that were created at a higher level. I don't want to completely remove access to the filters/dashboards/repo as they should be able to manage items at their level and below, but don't want them being able to look into the items that were created at a higher level, since they're not a higher level user that should ...more »
I often have trouble getting powershell and other scripts to work via automated tasks. I can run them directly on the server or workstation and they work just fine, but then I run into trouble when running it as a task. The frustration is that it takes a while to run the tasks through the dashboard, so you end up running and waiting. Then it errors out so you come back to it, modify your script or config, run it again... ...more »
When you add a script check to a system, the first window lets you choose the script to add and shows the description at the bottom when you select a script. The second window lets you enter the command line and timeout. But, does not show the description or usage notes. I usually put examples of proper command line syntax in the usage notes. If a tech can't remember the syntax, they have to close that window, open the ...more »
I would like for the N-Central probe to be able to run SNMP SET commands and for these to be save as a script type object that can be run on demand or integrated into healing processes. Healing processes need to be to run the SNMP script against third party devices. For example, if I have a PoE powered wireless access point or security camera, if the connection service shows the device to be down, then I would like it ...more »
When selecting which Script or AMP to run, it would be very helpful if the search in the drop down was a contains instead of a starts-with.
After running a script or amp, they are left in the cache/temp folders for anyone to be able to access.
Rather than having to update them to obfuscate or self-delete, it would be nice if they could just be encrypted so the IP is protected.
Using custom script checks (24/7 or daily) you might need to pass some credentials, e.g. for vSphere-host to run VMware-scripts. By using the parameter-textbox you can pass these details but they will be visible in the list of checks in dashboard and reports. (screenshot attached)
It would be great to hide these information and make them avalible by editing these checks only.
The only way to schedule a script once is on the overview page.
I would like to see the script schedule is also available on the opened asset.