Kosken

Product

From a failed signal to a checked fix

Kosken opens an incident when a signal fails, writes the root cause with evidence, and, if a fix is needed, proposes a signed recipe. Models write text. Code makes every decision that changes a machine.

Free for up to 5 machines. Every machine starts in audit mode: Kosken reads and reports, and changes nothing.

Five steps, from alert to fix

Models write text in three of the steps. Code makes every decision that changes a machine.

  1. A signal fails

    An agent on the machine reports a fact, for example disk use above 90 percent. A rule opens the incident. code

  2. Triage

    A model reads the signal and proposes a severity and a class. A safety classifier checks the output. model, then code

  3. Diagnosis

    A model reads evidence from the machine and writes the root cause analysis. It can end with conclude, which takes no action. It has no tool to close an incident. model

  4. Report

    The report cites evidence IDs. A check flags each claim that has no evidence. model, then code

  5. Execution

    The model selects a recipe from a closed, signed catalog. Five gates in code decide whether it runs, waits for a person, or stops. A separate process on the machine runs it and checks the result. code

One page for each incident

The incident page holds the signals, the triage, the diagnosis, the report, the proposal, the decision of the person, the run and the check of the fix, with the time of each stage.

Kosken incident page for INC-32: a container stopped on a test machine. The root cause report, the approval of docker.start, the check of the fix, and the time of each stage.
Incident 32 on a test machine of the authors.

After the fix

The fix is checked

After a recipe runs, its verify step checks the machine, and Kosken checks that the signals cleared. Only then is the incident resolved.

A failed check rolls back once

When the verify step fails, or the signal stays, Kosken runs the rollback of the recipe one time, if the recipe has one. Then a person must act.

A refused action does not wait in silence

When the gates refuse the action of a diagnosis, the incident goes to a person at once, with the recipe and the reason.

Memory of past incidents

Kosken keeps the past incidents and the fixes that worked. The diagnosis can read them for the same machine.