Nagios Feature
Posted: Mon Sep 21, 2015 10:36 am
How can I achieve below requirement in XI
Automatic and User performed action for event generated in the Nagios (example: If any services went down on a system Nagios event should restart the service automatically or User performed)
· Instruction area for each Events in the Nagios (Instruction text for event to get more details )
· Drill down the Performance Usage to understand the exact issue.(example CPU Utilization Drill down to Process table to identify the exact process which was utilizing the CPU during the window.)
· User access control on Nagios console for end user.
· Event Correlation to suppress duplicate events and Auto acknowledge on Nagios.
Automatic and User performed action for event generated in the Nagios (example: If any services went down on a system Nagios event should restart the service automatically or User performed)
· Instruction area for each Events in the Nagios (Instruction text for event to get more details )
· Drill down the Performance Usage to understand the exact issue.(example CPU Utilization Drill down to Process table to identify the exact process which was utilizing the CPU during the window.)
· User access control on Nagios console for end user.
· Event Correlation to suppress duplicate events and Auto acknowledge on Nagios.
tomatic and User performed action for event generated in the Nagios (example: If any services went down on a system Nagios event should restart the service automatically or User performed)
· Instruction area for each Events in the Nagios (Instruction text for event to get more details )
· Drill down the Performance Usage to understand the exact issue.(example CPU Utilization Drill down to Process table to identify the exact process which was utilizing the CPU during the window.)
· User access control on Nagios console for end user.
· Event Correlation to suppress duplicate events and Auto acknowledge on Nagios.
Automatic and User performed action for event generated in the Nagios (example: If any services went down on a system Nagios event should restart the service automatically or User performed)
· Instruction area for each Events in the Nagios (Instruction text for event to get more details )
· Drill down the Performance Usage to understand the exact issue.(example CPU Utilization Drill down to Process table to identify the exact process which was utilizing the CPU during the window.)
· User access control on Nagios console for end user.
· Event Correlation to suppress duplicate events and Auto acknowledge on Nagios.
Automatic and User performed action for event generated in the Nagios (example: If any services went down on a system Nagios event should restart the service automatically or User performed)
· Instruction area for each Events in the Nagios (Instruction text for event to get more details )
· Drill down the Performance Usage to understand the exact issue.(example CPU Utilization Drill down to Process table to identify the exact process which was utilizing the CPU during the window.)
· User access control on Nagios console for end user.
· Event Correlation to suppress duplicate events and Auto acknowledge on Nagios.
tomatic and User performed action for event generated in the Nagios (example: If any services went down on a system Nagios event should restart the service automatically or User performed)
· Instruction area for each Events in the Nagios (Instruction text for event to get more details )
· Drill down the Performance Usage to understand the exact issue.(example CPU Utilization Drill down to Process table to identify the exact process which was utilizing the CPU during the window.)
· User access control on Nagios console for end user.
· Event Correlation to suppress duplicate events and Auto acknowledge on Nagios.