edge-ocp-ci:generate-dashboard

Generate an interactive HTML dashboard for OpenShift nightly payload failures.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill edge-ocp-ci-generate-dashboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edge-ocp-ci:generate-dashboard
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/edge-ocp-ci/skills/generate-dashboard
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill edge-ocp-ci-generate-dashboard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, jinja2, requests, gsutil, click.

What problem does it solve?

It helps teams quickly identify and understand which OpenShift nightly payloads are failing on edge topologies so engineers can take targeted next steps instead of manually digging through CI artifacts.

Core Features & Use Cases

  • Monitors nightly payload health for edge topology streams (SNO/TNA/TNF) and highlights blocking failures.
  • Generates an interactive HTML dashboard that includes AI-enriched root cause analysis cards for blocking jobs.
  • Orchestrates CI skills and a payload-monitor tool to fetch payload/test/job data and merge analysis back into the report for fast triage.

Quick Start

Run edge-ocp-ci:generate-dashboard to produce an AI-enriched HTML dashboard for the default configured OCP versions and blocking payload failures.

Frequently Asked Questions about edge-ocp-ci:generate-dashboard

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

FAQPage Schema
How do I generate an OpenShift CI dashboard for nightly payload health failures?

To generate an OpenShift CI dashboard, this Skill orchestrates a payload-monitor run and follow-on blocking-job analysis to fetch Prow failures across edge topologies and patch AI root-cause analysis into an interactive HTML report.

What is AI-enriched root cause analysis for Prow failures on edge topologies?

AI-enriched root cause analysis for Prow failures automatically parses blocking-job markers from SNO, TNA, and TNF nightly payload streams, invokes deep analysis skills, and writes a compact JSON merged into an interactive HTML dashboard for fast triage.

How do I identify blocking jobs in OpenShift nightly payload streams for SNO and TNA?

You can identify blocking jobs by running a payload-monitor that targets OpenShift release streams, highlights blocking failures on edge topologies, and generates actionable next-step guidance for engineers.

Do I need Python and Jinja2 to generate an interactive HTML dashboard for CI monitoring?

Yes, generating the interactive HTML dashboard requires Python3 along with Jinja2, requests, gsutil, and click dependencies to orchestrate the payload monitoring and template the analysis report.

What's the best way to triage OpenShift payload failures across edge topologies?

The best way to triage OpenShift payload failures is to generate an AI-enriched dashboard that automatically merges root-cause analysis and next-step guidance for blocking jobs into a single interactive HTML report.

Why does my OpenShift nightly payload health dashboard show missing blocking-job analysis?

Missing blocking-job analysis in the dashboard occurs when the payload-monitor fails to parse blocking-job markers or cannot invoke the appropriate deep analysis skills to write the compact analysis JSON into the final HTML report.