microshift-dev:analyze-start-time

Parse MicroShift journal logs to produce a service startup timing table.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts MicroShift journal logs into actionable service-by-service startup timing statistics, so you can quickly identify slow or inconsistent components during bring-up and restarts.

Core Features & Use Cases

  • Service startup timing table: Produces a complete, sorted timing table with per-service runs and performance metrics.
  • MicroShift overall and per-service analysis: Summarizes overall startup plus detailed timings extracted from READY log lines.
  • Restart-aware reporting: Counts restarts and derives service statistics across each start instance for trend visibility.

Example: When a MicroShift edge node becomes slow to become ready, run this against the collected journal logs to pinpoint which service(s) dominate mean startup time and how variable those timings are.

Quick Start

Run /microshift-dev:analyze-start-time <journal-logs> to generate the mandatory service timing table from your MicroShift journal logs.

Frequently Asked Questions about microshift-dev:analyze-start-time

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

FAQPage Schema
How do I analyze MicroShift journal logs to find which services are slow to start up?

To analyze MicroShift journal logs for slow startup, this Skill parses MICROSHIFT READY and SERVICE READY log patterns to extract per-service timing statistics. It generates a performance table sorted by mean startup time to pinpoint delays.

What is the best way to compare MicroShift service startup performance across multiple restarts?

The best way to compare MicroShift service startup performance across restarts is to analyze collected journal logs. This Skill counts restarts and derives service timing statistics across each start instance for trend visibility.

Can I use journal logs to validate MicroShift service readiness behavior during edge bring-up?

Yes, you can use journal logs to validate MicroShift service readiness behavior during edge bring-up. The Skill extracts overall and per-service timings from READY log lines to confirm readiness and identify inconsistent components.

Do I need to install any dependencies to extract startup timing stats from MicroShift logs?

No dependencies are required to extract startup timing stats from MicroShift logs. You simply run the Skill against your collected journal logs to parse the READY log patterns and produce the sorted service performance table.

Why does MicroShift take a long time to become ready and how can I identify the bottleneck?

MicroShift may take a long time to become ready if a specific service dominates startup time. By parsing journal logs, this Skill identifies which services have the highest mean startup time and variability to locate the bottleneck.