data-health-monitor

Aggregate data health signals from streams, jobs, schema, and quotas via the LYTICS API.

4|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/lytics/agent-skills --skill data-health-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-health-monitor
Source: https://github.com/lytics/agent-skills/tree/main/data-health-monitor
Command: npx skills add https://github.com/lytics/agent-skills --skill data-health-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates health signals across streams, jobs, schema, and quotas into a single actionable report, enabling quick validation of data flow.

Core Features & Use Cases

  • Stream health checks to verify data flow and timeliness
  • Job status monitoring to detect stalled or failed processes
  • Schema health insights including identity, PII, and stale fields, plus quota awareness

Quick Start

Run the health monitor to generate a complete data health report for streams, jobs, and schema.

Frequently Asked Questions about data-health-monitor

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

FAQPage Schema
How do I monitor data pipeline health across streams, jobs, and schema definitions?

You can monitor data pipeline health by running a single command that aggregates status signals across streams, jobs, schema, and quotas into one actionable report. It verifies data flow, detects stalled jobs, and flags stale schema fields.

What is included in a data health check for streams and jobs?

A data health check includes stream health verification for data flow timeliness, job status monitoring to detect stalled or failed processes, and schema insights covering identity, PII, and stale fields, plus quota awareness.

Do I need an API token to check data health for my pipelines?

Yes, you need an API token to check data health. The monitor reads streams, jobs, and schema health endpoints via the API using this token to compile a unified report for your pipelines.

Can I use this for ongoing data pipelines or only periodic health reviews?

You can use this for both ongoing data pipelines and periodic health reviews. It is applicable to continuously checking data flow across multiple streams, jobs, and schema definitions.

What is the best way to consolidate schema health and quota signals into a single report?

The best way to consolidate schema health and quota signals is to run a health monitor that aggregates identity, PII, stale fields, and quota awareness into one unified report for quick validation of data flow.

Why does my data health report show stalled jobs and stale schema fields?

A data health report shows stalled jobs and stale schema fields because it actively monitors job status to detect failed processes and evaluates schema definitions to flag stale fields for pipeline maintenance.