OR
OpenRemedy

Policies

Visual flow editor for triggers and actions.

Alert-handling and proactive-monitoring policies. Each policy is a visual flow — trigger → action → recipe — applied over a set of servers.

List

Route: /policies Role gating: read for all; create / edit / delete require admin.

Card grid showing name, enabled toggle, flow preview, and scope (global / server_role / server).

Actions

  • New policy. Modal asks for the name; saving routes to the flow editor for the new policy.
  • Edit / Delete buttons on each card.

Editor

Route: /policies/{id} Role gating: admin.

Header

  • Editable name field.
  • Save Flow / Delete buttons.
  • Inline server-assignment selector — add or remove servers this policy applies to.
  • Enabled toggle.

Flow editor

Visual canvas with three node types.

  • Trigger. What fires the policy. Supported types: port, service, url, docker, recipe_check (runs an Ansible check on a schedule), cpu, memory, disk, log (regex match).
  • Condition / branch. Optional logic between trigger and action.
  • Action. Typically propose recipe X or auto-execute recipe X if low-risk. Subject to the global approval gate.

Flow changes auto-save to the database. Disabling a policy via the toggle suspends it without deleting the definition.


Related routes

  • recipes — actions invoke recipes
  • servers — policies target servers and server roles
  • incidents — policy triggers create incidents