What is Auto Healing?
Auto Healing is a feature that minimize business impact from unnecessary downtimes for problems that Nodinite by taking an appropriate corrective action. Manual labour is associated with costs, and out of office hours are even more costly. With the Nodinite Auto Healing feature you will not only keep business-critical services running, you will also save money and your business will perceive a higher quality of your service.
Technically; Auto Healing is a feature that executes Remote Actions when the evaluated state for a monitored Resource matches your configuration. It is the responsibility of the Monitoring Service to detect the problem and execute appropriate corrective action according to your configuration.
|Keeps business-critical resources online||Log Audited operations||Generally available on all Resources|
|Make your business enjoy a higher perceived quality of service||All operations in Nodinite are log audited, avoid any blame game discussions by knowing who was involved human or machine was||No limits - All monitored resources with Remote Actions can benefit from the auto-healing feature|
- Perform Remote Actions automatically
- Generally available for almost all Nodinite Resources
- Log Audited operations- You know if human or machine performed the Remote Actions
- Highly configurable with logic defined by a Nodinite Administrator
- No limit on number of configurations
- Enable/Disable configuration - Temporarily disable
- Resources with auto-healing enabled are marked with the ambulance icon in Monitor Views and the Resources Overview list
Below is a table with just a few examples taken from our customers and partners, feel free to contribute with your business case where the Nodinite auto-healing feature saved time end money for you by automatically execute remote actions for you.
|Monitoring Agent||Scenario||Executed Action||Business case|
|Windows Service||Windows Service has stopped||Start||Avoid any impact for your business by keeping Windows Services in the desired state|
|BizTalk||Receive Location has stopped||Enable||Keeps your receive locations enabled, BizTalk Receive locations may stop due to short default settings and external dependencies being offline (maintenance, reboot after being patch)|
|BizTalk||Sudden loss of Tracking on single port||Enable Tracking||Don't lose tracking data anymore. Tracking settings on default pipelines can get lost after deployment|
|SQL/SSIS||SSIS package fails to run due to missing file||Run SSIS Package||Your partner did not send the weekly file in time and therefore the SSIS packages fails to run. Have Nodinite Re-run this job a few times for you before either "giving" up or succeeds because the file was resent or sent just late|
|Logic Apps||Disabled Logic App||Enable||After deployment someone forgot to enable the Logic App. For this example you should allow for at least 15-30 minutes before retrying operation to not interfere with deployments in progress|
|MuleSoft Anypoint||Stopped Connector||Start Connector||Someone accidentally stopped a Connector. See previous scenario for additional details on this similar case|
To prevent Nodinite from performing Auto healing actions you can either:
- Disable Auto healing configuration on selected Resource - see the 'Add or manage Resource' user guide for further details and instructions
- Set Nodinite in maintenance mode
- Stop the Monitoring Service temporarily
Stopping the Monitoring Service is not recommended since you have no monitoring at all then for the duration of the stop
If you still have any questions, or have trouble with Auto Healing please contact us at email@example.com