spark-operations-cli

Name: spark-operations-cli
Availability: InStock
Author: Microsoft

Diagnose Spark job failures and Livy session health using read-only REST APIs.

952|267|Updated Feb 17, 2026

Search Tags:#monitoring #logs #diagnostics #triage #spark #fabric #livy

Ready to run

npx skills add https://github.com/microsoft/skills-for-fabric --skill spark-operations-cli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spark-operations-cli
Source: https://github.com/microsoft/skills-for-fabric/tree/main/plugins/fabric-operations/skills/spark-operations-cli
Command: npx skills add https://github.com/microsoft/skills-for-fabric --skill spark-operations-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Spark diagnostics skill helps Fabric teams quickly identify why a Spark job, Livy session, or Lakehouse operation failed, triage performance issues, and surface actionable remediation recommendations using read-only APIs and Spark monitoring data.

Core Features & Use Cases

End-to-end diagnostic workflows for Spark job failures, Livy session health, and performance bottlenecks across notebooks, pipelines, and lakehouses.
Reads Spark Advisor results, driver/executor logs, and resource usage to produce prioritized findings and concrete fixes.
Supports offline analysis via Spark History Server when online data is insufficient.

Quick Start

Run the Spark diagnostic workflow against a workspace to triage a failed notebook.

Frequently Asked Questions about spark-operations-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose Spark job failures in Fabric?▼

To diagnose Spark job failures in Fabric, you can use read-only REST APIs and Spark monitoring data to surface root causes. The workflow analyzes Spark Advisor results, driver logs, and resource usage to provide prioritized findings and concrete fixes.

What is the best way to triage Livy session health issues?▼

Triage Livy session health issues by applying a diagnostic workflow that reads session state and Spark monitoring data. This identifies failures and performance bottlenecks, surfacing actionable remediation recommendations to support rapid triage.

Can I use read-only APIs to troubleshoot performance bottlenecks in Fabric lakehouses?▼

Yes, you can use read-only REST APIs to troubleshoot performance bottlenecks in Fabric lakehouses. The diagnostic workflow analyzes resource usage and Spark Advisor results to produce structured reports for quick troubleshooting.

Do I need a local Spark History Server to analyze Fabric Spark logs?▼

You do not need a local Spark History Server for standard analysis, but it provides optional offline analysis when online data is insufficient. Online diagnostics primarily rely on read-only REST APIs and Spark Advisor results.

Why does my Fabric notebook fail and how do I find the root cause?▼

Your Fabric notebook may fail due to Spark job errors, Livy session issues, or resource bottlenecks. Find the root cause by running a diagnostic workflow that reads driver logs and Spark Advisor results to surface prioritized findings.