Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 42 ] [+]
Currently there is no way to auto define notification triggers for each of the probes living at SO > Administration > Probes page. Please provide a method to do this.
Add persistence to filter creation that if the checkbox isn't checked the filter will auto delete after x amount of time. The x amount of time can be configured on a SO, Customer, or user basis.
Allow Integration with FortiSIEM (exportation of service status', device information, etc).
Add Liongard Integration into N-Central. This can supplement the information gathered via the N-Central agent and provide a data validation set and/or provide more information about the network.
Add notes section to each rule so we can track changes made within the rule itself.
Currently the Probe will download updates whenever it wants, allow the capability to tell the Probe when it is ok to download updates and when it is not.
Based on administrator defined parameters, allow the capability to restrict which users are visible for accounts to be managed via Domain User Management. This would allow delegation of account management to individuals who are authorized to manage subset A but not subset B.
Currently we are stuck with whenever N-Central server decides to sync data between the N-Central Report Manager and the N-Central Server. It would be great to be able to increase the time frame that data is sync'd and/or to be able to the change time(s) that the data syncs.
Allow a manual resync of the N-Central server database and the Report Manager database. Currently this is hard coded to 1 hour. It would be great to be able to kick it off from our end instead of having to rely on Support.
The reason this is needed is because we are integrating with another system and would like changes to propagate faster than 1 hour to provide real time information to our clients.
If a client has been in downtime for "x" amount of downtime, allow the sending of an alert message to a targeted recipient, either the user who put the client in downtime or a system admin.
When a probe is removed from an environment and the tasks are switched over, it would be great to have the discovery jobs automatically switch over as well with perhaps an email notification to the account admins that the jobs were switched over. As it is now, if a new probe is stood up in an environment there is no easy way to switch the discovery jobs and if they aren't switched then the jobs are lost.
Allow the scheduling of the automatic N-Central agent installation (for instance, you know that a machine will be online 4 hours from when it is added to N-Central and you would like to have N-Central try then). Currently, this functionality does not exist and if the system tries x number of times and fails then it gives up. This leaves alot of machines without the agent installed which doesn't help admin'ing them.