hosted-studio-debug

Debug GenLayer Studio Kubernetes deployments using ArgoCD CLI status checks and log analysis.

157|60|Updated Mar 16, 2024
One-click install
npx skills add https://github.com/genlayerlabs/genlayer-studio --skill hosted-studio-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hosted-studio-debug
Source: https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/hosted-studio-debug
Command: npx skills add https://github.com/genlayerlabs/genlayer-studio --skill hosted-studio-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers debug issues with GenLayer Studio deployments in Kubernetes environments by leveraging the ArgoCD CLI for status checks and log analysis.

Core Features & Use Cases

  • Comprehensive Status Checks: Monitor the health of ArgoCD applications and their associated Kubernetes resources (Pods, Deployments, Services).
  • Log Analysis: Quickly filter and view logs from specific components like consensus workers, JSON-RPC services, and webdrivers to identify errors and timeouts.
  • Use Case: When a GenLayer Studio deployment is experiencing transaction timeouts, this Skill can be used to pinpoint the exact consensus worker replica that is failing and analyze its logs for root causes like an unresponsive GenVM Manager.

Quick Start

Check the overall application health for the 'studio-prd-workload' application.

Frequently Asked Questions about hosted-studio-debug

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

FAQPage Schema
How do I debug GenLayer Studio deployments in Kubernetes?

Debug GenLayer Studio deployments in Kubernetes by using the ArgoCD CLI to check application status, list Kubernetes resources, and analyze component logs to pinpoint failures.

How do I troubleshoot transaction timeouts in GenLayer Studio?

Troubleshoot transaction timeouts in GenLayer Studio by using ArgoCD to pinpoint the exact failing consensus worker replica and analyzing its logs for root causes like an unresponsive GenVM Manager.

Can I analyze logs for specific components in a GenLayer Studio deployment?

Yes, you can filter and view logs from specific components like consensus workers, JSON-RPC services, and webdrivers to identify errors, timeouts, and external API failures in your deployment.

Do I need ArgoCD CLI access to troubleshoot GenLayer Studio pods?

Yes, troubleshooting GenLayer Studio deployments requires ArgoCD CLI access and knowledge of Kubernetes application structures to check application health and analyze pod restarts.

What is the best way to monitor ArgoCD application health for GenLayer Studio?

Monitor ArgoCD application health for GenLayer Studio by checking the status of the application and its associated Kubernetes resources, including Pods, Deployments, and Services.

Why does my GenLayer Studio workload keep experiencing pod restarts?

Pod restarts in GenLayer Studio workloads can be identified by checking application status and analyzing logs for specific components to isolate root causes like unresponsive managers or external API failures.