Workflow library

The workflow library is a set of workflows Firefight ships and keeps up to date, such as a disk space check, that you use as they are or copy to make your own. It is also where you export your workflows as files and import them into another workspace.

Open Workflows under Halon in the dashboard and choose the Library tab. It holds two lists, Your workflows and Firefight’s library.

Every member can read the tab, use a library workflow and import a file, unless an admin took making workflows away from them (see Who can make workflows). Taking a newer library version into a draft or keeping your own are an admin’s, as is publishing.

Firefight’s library

Firefight’s library holds these workflows:

Workflow	What it does
Disk space check	Looks at disks, volumes and databases filling up and works out the day each runs out at the current rate
Certificate check	Looks at the TLS certificates on the domains you run and finds the ones that expire soon or will not renew
Error budget check	Looks at services spending their error budget faster than it lasts and works out the day it runs out
Cost check	Reads the spend your providers report against the months before and finds what grew
Scheduled check	Looks at whatever your notes describe on a schedule, such as a queue that should never grow

Each one tells the owning team once about each problem it finds, and again only when it gets worse. Each row shows what it does, what starts it, how many steps it has and its version. One that is already in use in your workspace names the workflows made from it.

Press Use, name the workflow, answer any question it asks, and pick how to take it:

Choice	What happens when Firefight ships a newer version
Use it as it is	Your workflow moves to the new version. You can still change what starts it, such as its schedule, and keep following the library
Make it your own copy	Your workflow stays as it is. You are told a newer version is out, with what changed

Scheduled check asks What should Halon check? and is not made without an answer. The others ask nothing here. When you run one by hand, it asks what Halon should look at closely or leave alone, and looks at everything it can read unless you say.

Press Make the draft. Either way the workflow starts as a draft, and runs once someone publishes it.

A workflow you use as it is becomes your own copy as soon as someone changes its steps and publishes them. From then on it is told about new versions instead of moving with them.

When a newer version is out

Under Your workflows, the From column says where each workflow came from: Your own, Firefight’s workflow it follows with its version, or your copy of one. A copy is marked when a newer version is out, such as Version 2 is out. Click the mark, or See Firefight’s version 2 in the workflow’s menu, to see each change as a sentence, such as a step that was added or a setting that changed.

Take it into a draft opens a new draft holding Firefight’s version, with your workflow’s own trigger. Look at it and publish it when it is right. Taking a version is refused while the workflow already has an open draft, so publish or discard that one first.
Keep mine leaves your workflow as it is. You are told again when a newer version comes out.

Exporting and importing

Your workflows lists every workflow in the workspace, where each came from, and whether it is published.

Export as a file, in a workflow’s menu, downloads its published version, or its draft when nothing is published yet, as a .workflow.json file.
Import a workflow reads such a file into a new workflow, named as the file names it unless you give it another name. It arrives as a draft, and runs once someone publishes it.

A file is refused when it is not a Firefight workflow, when it was written by a newer version of Firefight, when it is larger than 512 KB, when it takes a name another workflow already answers to, or when it looks like it holds a password, key or token. A step that needs a credential names the connection that holds it, so an exported workflow never carries one.