Skip to main content

A utility for triaging must-gather output

Project description

must-triage

When things go wrong with OpenShift or OpenShift Container Storage, we sometimes use must-gather or ocs-must-gather to collect logfiles and other documents to diagnose issues. While those tools are useful in that they can show us a lot about the state of the system(s), they don't offer anything to help process that information.

must-triage is a very small utility to aid in identifying problems recorded in must-gather output.

Features

Currently, must-triage knows about the following potential issues:

OpenShift (OCP)

  • Unparseable YAML files
  • Pods not in ready state
  • Operators who haven't reported success
  • YAML files which contain a top-level error field

OpenShift Container Storage (OCS)

  • Empty JSON files
  • Unparseable JSON files
  • Ceph health not HEALTH_OK
  • Logfiles which mention a panic

Teaching it to identify new issues is not difficult; PRs warmly welcomed!

Installation

pip install must-triage

Usage

must-triage /path/to/must-gather/output

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

must_triage-0.3.4.tar.gz (23.5 kB view hashes)

Uploaded source

Built Distribution

must_triage-0.3.4-py3-none-any.whl (20.0 kB view hashes)

Uploaded py3

Supported by

AWS AWS Cloud computing Datadog Datadog Monitoring Facebook / Instagram Facebook / Instagram PSF Sponsor Fastly Fastly CDN Google Google Object Storage and Download Analytics Huawei Huawei PSF Sponsor Microsoft Microsoft PSF Sponsor NVIDIA NVIDIA PSF Sponsor Pingdom Pingdom Monitoring Salesforce Salesforce PSF Sponsor Sentry Sentry Error logging StatusPage StatusPage Status page