Overview

Callgoose SQIBS automation runs the fixes and routine tasks your engineers already know, in your own environment. You build it from three parts: profiles (where to run), actions (what to run) and workflows (in what order). A workflow can run when an incident opens, from an incident or a request, or from Slack, Microsoft Teams and the mobile app.

You need
Permission to manage automation in SQIBS
Where
Automation in the SQIBS menu
Result
Repeatable, approved fixes that run in seconds

How it fits together

Profile
Where it runs
Version and connection details: an SSH host, a kubeconfig, an Ansible inventory.
Action
What it runs
A script, a playbook, a command. Yours, or a copy of a Callgoose action.
Workflow
In what order
Actions and delays in sequence, with custom variables.
Run
When it runs
When an incident opens, from an incident, from a request, or by API.

Set it up

  1. Create a profile for the environment: automation profile. To run inside your network, first add a runner profile and install the Callgoose automation runner.
  2. Create an action for each task: automation action. You can start from a Callgoose action and change it.
  3. Create a workflow that runs the actions in order: automation workflow.

Run a workflow

From How
An incident (web or mobile app) Open the incident, click Run Workflow, choose the workflow and run it.
Slack or Microsoft Teams Click Run Workflow on the incident message and choose the workflow.
A request Create a request for the workflow, or click Create Request for Workflow on the workflow. See requests.
The API Send a request to the Request API with the workflow's Public ID. See API: request.
Automatically Link the workflow to an API or email filter in the service, so it runs when that filter opens an incident (below).

If the workflow has custom variables, SQIBS asks for their values before it runs. When you run it from an incident you can also choose Resolve the incident if the workflow is successful.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when a monitoring tool reports a stopped service, SQIBS runs a workflow that restarts it and checks it is answering.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: