Varqeni Help

Change the autopilot policy

Updated 11 November 2026

The policy names each cause the autopilot may fix, the action, the confidence it needs, how often it may act and who is told.

AvailabilityFor the person who runs Varqeni for your team. In early access that is usually Fortis, working with you.

Steps

  • Edit /etc/opsagent/autonomy.yaml on the host.
  • Run sudo /opt/opsagent/venv/bin/opsagent autonomy-check. It refuses mistakes and prints what the policy allows.
  • The autopilot reads the policy every 15 seconds; no restart is needed.
  • Set enabled: false to switch the autopilot off.

What you should see: Policies in the console shows the new rules, or the error if the file is invalid.

What it can and cannot do

Can

  • Change which faults the autopilot fixes, at what confidence and how often, checked before it applies.

Cannot

  • Add an action that is not built in, or one that is never automated.

Before adding a rule

Fortis adds a fix to the policy only after closed-loop trials on that fault pass. Ask Fortis before adding a rule.

Still stuck? Contact support or email info@fortisdatagroup.com.