What is Auto Healing?
Nodinite Auto Healing delivers proactive, automated monitoring and remediation for your integration landscape. This feature detects and fixes issues within minutes—no manual intervention, risky server access, or late-night troubleshooting required.
- ✅ Resolves problems within minutes with zero-touch automation
- ✅ Reduces downtime and operational costs
- ✅ Full audit trail and secure, policy-driven actions
Walkthrough: configure an entry on a BizTalk Receive Location, disable it, and watch Auto Healing enable it again, with every attempt in the Log Audits.
Welcome to Monitoring on Steroids!
Auto Healing revolutionizes operations by automatically detecting and fixing issues—without your team logging in, using VPNs, or handling admin credentials. Forget late-night RDP sessions and expensive downtime. Nodinite Auto Healing keeps your integrations and services running, saving money and delivering higher service quality your business can brag about.
Auto Healing triggers Remote Actions when monitored Resources report a problem—following your rules, fast and securely.
Depending on your configuration, Nodinite can postpone the immediate alert for the affected Resource while Auto Healing gets a chance to recover the problem first.
Tip
Auto Healing is available for almost every Resource monitored by Nodinite!
Auto Healing minimizes business impact from unnecessary downtime by taking corrective action automatically. Manual labor is costly, especially after hours. With Nodinite Auto Healing, you keep business-critical services running, save money, and deliver higher perceived service quality.
Technically: Auto Healing executes Remote Actions when the state the Monitoring Agent reports for a monitored Resource matches your configuration. The Auto Healing Worker in the Monitoring Service finds the matching Resources and runs the corrective action through the agent, according to your rules.
How Auto Healing Works
reports state"] --> MS["fa:fa-watch-fitness Auto Healing Worker
runs every 5 minutes"] MS -->|"no entry matches"| OK["fa:fa-circle-check OK
nothing to do"] MS -->|"reported state matches
an Auto Healing entry"| AH["fa:fa-ambulance Auto Healing
runs the Remote Action"] AH -->|"retry after Interval,
up to Attempts"| AH AH -->|"Resource recovers"| OK AH -->|"still failing after all attempts
(alert can be postponed while healing runs)"| AL["fa:fa-bell Alert
through Alarm Plugins"] AH -.->|"every action"| AU["fa:fa-user-tag Log Audit"] style AG fill:#2678BD,color:#fff style MS fill:#2678BD,color:#fff style OK fill:#93d16d,color:#000 style AH fill:#FFD525,color:#000 style AL fill:#c33d34,color:#fff style AU fill:#3F827B,color:#fff
Blue: the agent reports the state and the Monitoring Service's Auto Healing Worker checks it. Green OK: no action needed, or the Resource recovered. Yellow: Auto Healing is working on a configured state, retrying per the configured Attempts and Interval. Red: the problem remains, and users are alerted through Alarm Plugins. Teal: every action is written to the Log Audits.
Each Auto Healing entry on a Resource maps one state to one Remote Action, with Attempts and Interval as its retry policy. You configure the entries on the Resource's Configuration tab; see Add or manage Resource.
What Happens When
- When it runs: the Auto Healing Worker in the Monitoring Service runs every 5 minutes, and once when the service starts. Each run picks the Resources whose state equals the When in state of an enabled entry, and runs that entry's Action through the Monitoring Agent, if the agent is alive and the action exists for the Resource's Category. In the walkthrough above, the Receive Location turned Error at 22:20:22, the worker ran Enable at 22:24:30, and the agent reported OK at 22:25:22.
- Which state is matched: the state the Monitoring Agent reports, before Expected State is applied. Use Expected State for conditions that are intentional, and Auto Healing for conditions that should be fixed.
- Which actions: only Remote Actions that change something. Read-only actions such as Details are greyed out in the Action list ("'GET' methods are not allowed").
- Retries: the next attempt waits Interval seconds (10–7200) after the last one. The number under Attempts (1–50) is the total number of attempts: with 3, the Resource page shows "On attempt 1 of 3".
- When all attempts are used: the entry turns Error ("No attempts left"), and a warning is written to the Log Audits. Click Reset on the Resource page to put the entry back in the rotation.
- After a successful heal: at its next run, the worker marks the entry Successful once the Resource no longer reports the state. The attempts used are kept, so the Resource page shows "Succeeded after 1 of 3, 5 minutes ago", and Reset isn't offered. The next time the Resource enters the state, the entry goes back to Idle and a new cycle starts, counting attempts from 1. See How do I see that Auto Healing fixed a Resource?
- Postpone alerts (the snooze icon): while the entry is Idle or Pending for the Resource's current state, alerts for that Resource are held back. If the healing fails, the alert goes out as usual.
- Audit trail: every attempt is in the Log Audits, with the Source Nodinite Monitoring Service, the Function Auto Healing Worker, and an Operation like "Executed action 'Enable' in an attempt to auto-heal the Resource: 'SFTP Receive From File' … attempt 1 of 3".
The Manage Auto-healing configurations dialog, opened with Edit on the Resource's Auto-healing configuration card.
| Zero Downtime | Full Audit Trail | Works Everywhere |
|---|---|---|
| Keep mission-critical systems alive automatically. | Every Auto Healing action is log-audited. Human or machine, you'll know. | Use Auto Healing on any monitored Resource with Remote Actions. |
Key Features
Trigger Remote Actions automatically when issues are detected
Supported across almost all Nodinite Resources
Smart, configurable logic by your Nodinite Admins
Full Log Audited operations—know exactly what happened and who (or what) did it
No technical limit on number of healing configurations
Easily Enable/Disable per Resource
Visual indicator (ambulance icon) in Monitor Views and Resources Overview
Real-World Auto Healing Scenarios
See how businesses already save thousands and work smarter:
| Monitoring Agent | Scenario | Action | Business Value |
|---|---|---|---|
| Windows Service | Service stopped | Start | No downtime, seamless operations |
| BizTalk | Receive Location stopped | Enable | Keeps integration flows alive despite backend hiccups |
| BizTalk | Lost Tracking on a port | Enable Tracking | Never lose critical transaction data again |
| SQL/SSIS | Package fails due to missing file | Retry Package | Handles partner delays without manual intervention |
| Logic Apps | Logic App disabled post-deployment | Enable | Automatically fixes human errors in release processes |
| MuleSoft | Connector stopped | Start Connector | Recover without waiting for manual troubleshooting |
FAQ - Everything You Need to Know
Common problems not answered below and FAQ for the Monitoring Service can be found on the Troubleshooting page.
How do I configure Auto Healing?
Configuration is done per Resource: open the Resource, go to the Configuration tab, and click Edit on the Auto-healing configuration card. In Manage Auto-healing configurations, click Add, set When in state, Action, Attempts, and Interval, then click Confirm and close and Save. Check the Add or manage Resource guide for the full setup.
Good candidates are Remote Actions that are safe to repeat, such as Start on a stopped Windows service or a BizTalk Send Port, and Enable on a BizTalk Receive Location.
Important
Only enable Auto Healing where it won't interfere with controlled downtime events like deployments.
How do I temporarily disable Auto Healing?
You can use the following options:
Add a maintenance User Notification for the Monitor Views that hold the Resources—recommended! While it is active, the Auto Healing Worker skips every Resource in those Monitor Views.
Clear Enabled on an Auto Healing entry of a specific Resource; see the 'Add or manage Resource' user guide for further details and instructions
Stop the Nodinite Monitoring Service (not recommended—no monitoring at all!)
How can I see which Resources have Auto Healing?
Look for the Ambulance icon in the Auto-healing column of your Nodinite Monitor Views or the Resources Overview list.
The ambulance icon marks the Resources with Auto Healing.
Walkthrough: from the ambulance icon to the configured entry.
How do I find out which Remote Actions are configured?
Open the Resource and its Configuration tab. The Auto-healing configuration card lists each entry with its Progress, Enabled, When in state, Action, Attempts, and Interval.
The configured Auto Healing Remote Actions of a Resource, with their progress.
How do I see that Auto Healing fixed a Resource?
When the Resource no longer reports the state after an attempt, the Monitoring Service marks the entry Successful at the Auto Healing Worker's next run (every 5 minutes). You see it in three places:
The Progress column on the Resource's Configuration tab reads "Succeeded after 1 of 3, 5 minutes ago", as in the image above.
In the Resources Overview, the Successful choice of the Auto-healing State filter lists the Resource:
The Auto-healing State filter set to Successful.In Log Audit Search, an Info row from the Source Nodinite Monitoring Service reads "Marked 1 Auto Healing entry Successful, the Resource recovered after an attempt: …":
The audit row for an entry marked Successful.
Need Help?
Still have questions or want to optimize your Auto Healing setup? Contact our experts:
Next Steps
- Add or manage Resource
- Add or manage Monitor View
- Manage Monitoring Service
- Remote Actions - What users can run manually