skills.rest
Checkmk
CheckmkOFFICIAL
Explore all skills by this author →
Website𝕏@CheckmkGitHub

crash-report

Query and analyze Checkmk crash reports from crash.checkmk.com and local OMD sites.

2.3k|552|Updated Feb 20, 2019
Search Tags:#debugging#issue resolution#anonymization#checkmk#crash report#traceback analysis
One-click install
npx skills add https://github.com/Checkmk/checkmk --skill crash-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crash-report
Source: https://github.com/Checkmk/checkmk/tree/main/.claude/skills/crash_report
Command: npx skills add https://github.com/Checkmk/checkmk --skill crash-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of querying, analyzing, and understanding crash reports from Checkmk instances, significantly speeding up debugging and issue resolution.

Core Features & Use Cases

  • Query Crash Reports: Search and retrieve crash reports from crash.checkmk.com or local OMD sites.
  • Automated Analysis: Automatically explains crash tracebacks, identifies problematic code sections, and correlates them with the Checkmk codebase.
  • Test & Fix Workflow: Facilitates the creation of unit tests for identified crashes and guides the fixing process.
  • Use Case: When a Checkmk service crashes, use this Skill to quickly get details about the crash, understand the root cause by locating the faulty code, and even generate a test case to prevent regressions.

Quick Start

Use the crash-report skill to show the details for crash report abc-123.

Frequently Asked Questions about crash-report

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

FAQPage Schema
How do I analyze a Checkmk crash report from crash.checkmk.com?▼

To analyze a Checkmk crash report, query the crash ID from crash.checkmk.com or a local OMD site to fetch crash data, anonymize sensitive details, and automatically explain the traceback. This identifies problematic code sections for faster debugging.

What is the best way to debug a Checkmk service crash and prevent regressions?▼

The best way to debug a Checkmk service crash is to query the traceback to locate the faulty code, understand the exception, and generate a unit test. This facilitates a test-driven workflow to prevent future regressions.

Can I retrieve crash tracebacks from a local OMD site for debugging?▼

Yes, you can retrieve crash tracebacks directly from local OMD sites. The process queries local crash data, anonymizes sensitive information, and correlates the exception with the Checkmk codebase to identify the exact code location.

Does the crash report analysis process anonymize sensitive information from local OMD sites?▼

Yes, the crash report analysis process includes automated anonymization of sensitive information. It fetches crash data from crash.checkmk.com or local OMD sites and scrubs sensitive details before presenting the traceback explanation.

How do I identify the problematic code section causing a Checkmk exception?▼

To identify the problematic code section causing a Checkmk exception, run an automated traceback analysis. This correlates the crash data with the Checkmk codebase to pinpoint the exact code location and guide issue resolution.

Related Skills

Explore More Software Engineering Skills→
omega-bredomega-bred
6

asc-crash-triage

Analyze and summarize TestFlight crash reports and beta feedback.

Official
Advanced
xxihxxih
1

test-driven-development

Enforce red-green-refactor cycles with failing tests before implementation.

Community
Intermediate
delorenjdelorenj

skf-analyze-source

Analyze codebases to identify skillable units and generate recommendations.

Community
Advanced
paleoterrapaleoterra
2

crash-log-analyzer

Parse macOS crash logs to identify crash causes and debugging information.

Community
Intermediate