How to automate fixes with Optanik automations and playbooks

The two kinds of Optanik automation

• IF/THEN rules watch live device health.
• Scheduled jobs run scans, installs and maintenance on a clock.

Build an Optanik automation

1. Trigger. When conditions are met, or on a schedule.
2. Scope. Any device, a group, or one specific computer.
3. Conditions (IF/THEN rules). Build them from dozens of signals, such as CPU, free disk space, missing patches, a stopped service, a running process or an event log entry, and say how long the condition has to last.
4. Actions. Stack them: create or resolve an alert, send an email, run a script, reboot, restart a service, kill a process, install patches, open a ticket, and more, with waits and yes/no checks in between.

Start from an Optanik playbook

Most people start from one of the 162 playbooks, in categories such as security, patches, recovery and maintenance. Some are complete self-healing workflows. One notices an unhealthy computer, cleans up the disk, restarts services, installs critical patches, reboots if needed, checks again, and only calls a technician if that didn't work.

Use playbook adds it switched off, so you set its scope first, then turn it on.

Test and review Optanik automations

Every automation can be edited, duplicated, disabled, or run now to test it. History shows every run and how it went. Cooldowns and maximum runs keep a noisy condition from looping all night, and one alert covers the task rather than a ping per endpoint.