Thanks to the implementation of action models aimed at resolving incidents, the ServiceNav software allows to go further than the simple monitoring of the IS.
Use of action models in an operational context
When setting up an IS monitoring system, what is the point of using action models in daily IT operations?
Using action templates with ServiceNav
L'monitoring tool is generally used to monitor and control the proper functioning of its information system (IS).
Its objective is to issue alerts or display on a dashboard the events related to the health of the supervised IT services and equipment. It allows you to control its operation and alert the IT department in the event of incidents.
But why stop there?
The ServiceNav global IT monitoring software allows you to implement "action models" to go further than simple monitoring: incident or problem resolution.
Use case 1 Let's imagine that you are responsible for a server park in your company and that the disk space issue keeps causing you problems. Temporary space constantly full, etc.... You have of course put the storage spaces under supervision and, as every day, you receive a saturated space alert. So, before the disk is completely full, you have to connect to the server and clean up the folders to free up space. With ServiceNav, you have the possibility on the change of state of your service which monitors the disk space to launch automatically actions (PowerShell script, linux command ...) to do this work automatically.
Use case 2 In your operating procedures, a process is carried out every evening but regularly at the end of the process a Windows or Linux service does not restart, which will obviously generate an alert. The problem is that in the evening, you rather want to sleep than to connect to the system to restart this service. Once again, ServiceNav will help you with the "action templates". To do this, you just have to monitor the service in question and restart it if its status changes to critical (Service stopped).Discover our case studies
Setting up an action model for a supervised service
To add an action model, you just have to configure the supervised service from the technical operation screen. Here I select my TeamViewer service and I will configure it to restart automatically if its status changes to critical.
I select my model in the drop-down list (cf. How to set up an action template)
I select my model in the drop-down list (cf. How to set up an action template)
And now, every time my service goes into a critical state, the action model will restart it.
Warning: If you need to stop this service during an intervention, you will have to disable this model in ServiceNav otherwise it will restart automatically.
