collecting-cockroachdb-operator-escalation-packet

Collect diagnostic data from CockroachDB clusters for troubleshooting.

105|153|Updated Jun 24, 2020
One-click install
npx skills add https://github.com/cockroachdb/helm-charts --skill collecting-cockroachdb-operator-escalation-packet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collecting-cockroachdb-operator-escalation-packet
Source: https://github.com/cockroachdb/helm-charts/tree/main/skills/cockroachdb-observability-and-diagnostics/collecting-cockroachdb-operator-escalation-packet
Command: npx skills add https://github.com/cockroachdb/helm-charts --skill collecting-cockroachdb-operator-escalation-packet

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit is designed to assist in troubleshooting CockroachDB Operator issues by collecting a comprehensive set of diagnostic information, enabling efficient escalation to the appropriate support teams.

Core Features & Use Cases

  • Escalation Packet Collection: Automates the collection of Helm state, Kubernetes resources, logs, operation-specific evidence, pprof goroutine dumps, metrics, and a customer action timeline.
  • Compatibility: Supports CockroachDB Helm v2 charts and operator-managed crdb.cockroachlabs.com/v1beta1 resources.
  • Use Case: Before restarting a stuck operator or escalating an issue to TSC, use this Skill to gather all necessary information for a thorough investigation.

Quick Start

Use the 'collecting-cockroachdb-operator-escalation-packet' skill to collect an escalation packet for a CockroachDB Operator issue.

Frequently Asked Questions about collecting-cockroachdb-operator-escalation-packet

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

FAQPage Schema
How do I collect diagnostic data for CockroachDB Operator troubleshooting?

To collect diagnostic data for CockroachDB Operator troubleshooting, you can automate gathering Helm state, Kubernetes resources, logs, pprof goroutine dumps, and metrics into a comprehensive escalation packet for support teams.

What is included in a CockroachDB Operator escalation packet?

A CockroachDB Operator escalation packet includes Helm state, Kubernetes resources, aggregated logs, operation-specific evidence, pprof goroutine dumps, metrics, and a customer action timeline for thorough issue investigation.

Do I need specific Kubernetes permissions for CockroachDB log aggregation and data collection?

Yes, you need Kubernetes access and specific permissions for data collection and port-forwarding to successfully gather operational evidence and aggregate logs from the CockroachDB cluster.

Can I use this escalation packet collection for CockroachDB Helm v2 charts?

Yes, the escalation packet collection supports CockroachDB Helm v2 charts and operator-managed crdb.cockroachlabs.com/v1beta1 resources for compatibility with your existing deployments.

When should I gather an escalation packet for a stuck CockroachDB Operator?

You should gather an escalation packet before restarting a stuck CockroachDB Operator or escalating an issue to TSC, ensuring all necessary information is collected for a thorough investigation.