SparkForensics

Appearance

Detector catalog / Reliability

SFAIL

Failed stage

A stage failed and took its job down with it.

Outcome
Reliability
Scope
Judged per stage
Usual fix
A change in the job code
CI gate
No budget flag: gate it with --fail-on-introduced against a baseline

An example finding

Where you see it

Dashboard

The SFAIL tag marks it in the action region of the dashboard, among the widgets that rank a fix. Every affected stage is flagged, not only the worst.How to read it in the findings guide.

Agent (MCP)

An assistant can read this entry with the list_detectors tool and its background with get_finding_documentation. The call and the response below come from a real run of the MCP server.

Call

{
  "tool": "list_detectors",
  "arguments": {
    "type": "stageFailed"
  }
}

Response

{
  "count": 1,
  "detectors": [
    {
      "type": "stageFailed",
      "name": "failed stage",
      "tag": "SFAIL",
      "tagSharedWith": [],
      "family": "reliability",
      "pitch": "A stage failed and took its job down with it.",
      "region": "action",
      "scope": "stage",
      "fixEffort": "code",
      "thresholdSummary": "a stage that failed outright",
      "detectors": [
        {
          "detector": "stageFailed",
          "version": 1,
          "thresholds": {}
        }
      ],
      "pages": {
        "catalog": "docs/detectors/stageFailed.html",
        "guide": "docs/user-guide/understanding-findings.html#sfail"
      },
      "tuning": {
        "kind": "shared",
        "anchor": "#bottleneck-failures",
        "path": "docs/tuning-reference/bottleneck-failures.html#bottleneck-failures"
      },
      "gate": null
    }
  ]
}

get_finding_documentation call

{
  "tool": "get_finding_documentation",
  "arguments": {
    "type": "stageFailed"
  }
}

Its response, with each Markdown body replaced by its length

{
  "type": "stageFailed",
  "name": "Failed Stage",
  "detectionDoc": {
    "tag": "SFAIL",
    "title": "Failed stage",
    "content": "<736 characters of Markdown>"
  },
  "tuningDoc": {
    "anchor": "#bottleneck-failures",
    "title": "Task Failures",
    "content": "<7414 characters of Markdown>"
  }
}

CI (CLI)

List this entry from the command line. The output below is a real run of the command. Budgets and exit codes are in the CI guide. 

sparkforensics-analyze detectors --type stageFailed --format md
# Detectors (1)

## Reliability

| Tag | Type | Scope | Fix | Gate | What it finds |
| --- | --- | --- | --- | --- | --- |
| SFAIL | `stageFailed` | stage | code |  | A stage failed and took its job down with it. |

Report only this finding type for a run with --type:

sparkforensics-analyze <event-log> --type stageFailed --impact critical,warning,info

It has no budget flag. Fail a build on a new one by comparing against a baseline with --fail-on-introduced.

Airflow

The operator has no budget parameter for it. Use fail_on_introduced with a baseline.

check_spark_job = SparkForensicsOperator(
    task_id="check_spark_job",
    log_source=...,
    backend=SubprocessAnalyzeHook(),
    baseline_log_source=...,
    fail_on_introduced="critical",
)

The operator works per run, and its summary counts findings per impact band. See the operator for its parameters.

How it is measured

Thresholds

A stage that failed outright.

stageFailed version 1

ThresholdDefault
No thresholds.

Each rule's impact bands and fixed fallbacks are in the threshold tables.

Override a default per run with --thresholds; see Tuning detector thresholds.

Docs