glean-status

Check glean pipeline health via pending tasks, activity, and configuration status.

Updated Apr 6, 2026

Search Tags:#automation #monitoring #troubleshooting #logs #pipeline #status

Ready to run

npx skills add https://github.com/vedantggwp/glean --skill glean-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: glean-status
Source: https://github.com/vedantggwp/glean/tree/main/skills/glean-status
Command: npx skills add https://github.com/vedantggwp/glean --skill glean-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables users to quickly assess the operational status of the glean data extraction pipeline, identifying pending tasks, recent activity, and configuration issues.

Core Features & Use Cases

Status Reporting: Provides real-time insights into the pipeline's queue lengths, last execution timestamp, and delivered fragments.
Troubleshooting: Highlights failed jobs and items in the outbox requiring attention to facilitate quick debugging.
Use Case: A developer wants to verify whether the glean worker is actively processing sessions and identify any bottlenecks or errors in the extraction workflow.

Quick Start

Run the glean status command and review the summarized status table to understand the current health of the pipeline.

Frequently Asked Questions about glean-status

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

FAQPage Schema

How do I monitor my data extraction pipeline health and check pending tasks?▼

You can monitor your data extraction pipeline health by running a status command that reports pending tasks, queue lengths, and recent activity. This provides real-time insights into the pipeline's operational state and delivered fragments.

What is the best way to troubleshoot failed jobs in a data pipeline?▼

To troubleshoot failed data pipeline jobs, review a summarized status table that highlights failed jobs and items in the outbox. This helps identify bottlenecks and configuration issues for quick debugging.

How do I verify if my data worker is actively processing sessions?▼

You can verify if your data worker is actively processing sessions by checking the last execution timestamp and recent activity logs. This confirms the worker is running and highlights any extraction workflow errors.

Can I check pipeline configuration status and outbox items without external dependencies?▼

Yes, you can check pipeline configuration status and outbox items without external dependencies. The status reporting mechanism runs as a standalone script to assess operational health and identify items requiring attention.

Why does my data extraction workflow have bottlenecks and how do I identify them?▼

Data extraction workflow bottlenecks can be identified by reviewing the status table for long queue lengths and pending tasks. This highlights failed jobs and outbox items that require immediate debugging attention.