skills.rest
dpla
dplaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dpla-ingest-status

Aggregate ingest status across hubs from status logs and orchestrator state.

35|12|Updated Jan 10, 2017
Search Tags:#monitoring#status#orchestrator#log-analysis#ingest#hub
One-click install
npx skills add https://github.com/dpla/ingestion3 --skill dpla-ingest-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dpla-ingest-status
Source: https://github.com/dpla/ingestion3/tree/main/.cursor/skills/dpla-ingest-status
Command: npx skills add https://github.com/dpla/ingestion3 --skill dpla-ingest-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill consolidates ingest status across multiple hubs, providing a single source of truth for operational insight and troubleshooting, reducing time spent jumping between logs and dashboards.

Core Features & Use Cases

  • Consolidated status view: aggregates per-hub and orchestrator state for quick health checks.
  • Live and historical context: supports live updates and review of past statuses via stored logs.
  • Use Case: Quickly identify which hubs are active, idle, or experiencing delays to triage ingest pipelines.

Quick Start

Run the status command to display current ingest state across hubs.

Frequently Asked Questions about dpla-ingest-status

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

FAQPage Schema
How do I monitor ingest status across multiple hubs in one view?▼

You can monitor ingest status across hubs by consolidating per-hub logs and orchestrator state into a single, queryable view. This allows quick identification of active, idle, or delayed pipelines for triage.

What ingest logs does the status aggregation read to diagnose failures?▼

Ingest status aggregation reads logs/status/*.status files and logs/orchestrator_state.json. It consolidates these sources to provide a consistent view for diagnosing failures and confirming hub activity.

Can I check live and historical ingest pipeline activity using orchestrator state?▼

Yes, checking live and historical ingest pipeline activity is supported. The system consolidates stored logs and orchestrator state to support both live updates and review of past hub statuses.

How do I identify which ingest hubs are idle or experiencing delays?▼

To identify idle or delayed ingest hubs, run the status command to aggregate current orchestrator state and per-hub logs. This provides a unified health check to quickly triage pipeline issues.

Do I need any external dependencies to consolidate ingest logs and orchestrator state?▼

No external dependencies are required to consolidate ingest logs and orchestrator state. The Skill operates using internal scripts to read status files and state data, providing a self-contained monitoring view.

What is the best way to troubleshoot ingest pipeline failures across hubs?▼

The best way to troubleshoot ingest pipeline failures is to aggregate logs and orchestrator state across all hubs. This single source of truth reduces time spent jumping between dashboards to pinpoint issues.

Related Skills

Explore More Software Engineering Skills→
dpladpla
35

dpla-orchestrator

Run the DPLA ingest orchestrator for harvest, mapping, enrichment, JSONL export, anomaly detection, and S3 sync.

Official
Advanced
dpladpla
35

DPLA Hub Ingest

Automate DPLA hub ingest from harvest to S3 sync on EC2.

Official
Advanced
terrylicaterrylica

mt5-log-reader

Parse MetaTrader 5 log files to validate execution and surface errors.

Community
Intermediate
aRustyDevaRustyDev
1

grafana-dashboards

Create and manage production Grafana dashboards for real-time metric visualization.

Community
Intermediate