skills.rest
zystem-io
zystem-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

troubleshoot-zymtrace-profiler

Diagnoses zymtrace profiler agent failures in Kubernetes using kubectl and helm workflows.

5|1|Updated May 17, 2026
Search Tags:#troubleshooting#kubernetes#helm#cuda#gpu profiling#zymtrace#nvml
One-click install
npx skills add https://github.com/zystem-io/zymtrace-skills --skill troubleshoot-zymtrace-profiler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot-zymtrace-profiler
Source: https://github.com/zystem-io/zymtrace-skills/tree/main/zymtrace/skills/troubleshoot-zymtrace-profiler
Command: npx skills add https://github.com/zystem-io/zymtrace-skills --skill troubleshoot-zymtrace-profiler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill troubleshoots the zymtrace profiler agent when it misbehaves, preventing reliable CPU/GPU profile collection.

Core Features & Use Cases

  • Symptom-to-root-cause routing: Guides diagnosis for CrashLoopBackOff, ImagePullBackOff, OOMKilled/restart cycles, missing NVML/GPU metrics, broken PC sampling, and profiler-side license/auth failures.
  • Agent-focused verification: Checks DaemonSet health, pod readiness, recent agent logs, and workload interception signals, while explicitly handing off to backend troubleshooting when the issue is downstream.
  • Kubernetes-first workflows: Uses kubectl and helm workflows to triage GPU vs CPU expectations, container configuration mismatches, and common cluster/runtime constraints.
  • Use Case: When the UI shows no GPU traces but the CPU path appears partially healthy, it walks the agent-side implant and GPU metrics prerequisites (cudaProfiler enabled, NVML discoverability, and PC sampling conditions) to determine whether the failure is agent-side or workload/backend-side.

Quick Start

Tell the Skill what you see (for example, “profiler pods CrashLoopBackOff” or “CPU profiles arrive but no GPU traces”) and confirm the profiler namespace and Helm release to get a targeted diagnosis and fix path.

Frequently Asked Questions about troubleshoot-zymtrace-profiler

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

FAQPage Schema
Why are GPU profiles missing in Kubernetes while CPU traces appear partially healthy?▼

Missing GPU profiles in Kubernetes while CPU traces work indicates an agent-side GPU metrics failure. This Skill diagnoses whether the issue stems from NVML discoverability, disabled cudaProfiler settings, or broken PC sampling conditions within the profiler DaemonSet.

How do I troubleshoot a profiler agent stuck in CrashLoopBackOff or ImagePullBackOff?▼

Troubleshooting a profiler agent in CrashLoopBackOff or ImagePullBackOff requires inspecting Kubernetes pod events and recent agent logs. This Skill validates the Helm release presence and DaemonSet health to match your specific error to a targeted fix path.

What causes OOMKilled restart loops in a Kubernetes GPU profiling DaemonSet?▼

OOMKilled restart loops in a GPU profiling DaemonSet are caused by container resource constraints or runtime limits. This Skill routes through an agent-focused decision tree to inspect workload interception signals and identify the failing profiler-side configuration.

How do I fix profiler-side license or authentication rejection errors in Kubernetes?▼

Profiler-side license or auth rejection errors in Kubernetes occur when the agent cannot validate its credentials. This Skill checks the profiler agent logs and Helm release configuration to determine if the failure is an agent-side authentication issue or a downstream ingest problem.

When should I defer profiler agent troubleshooting to backend ingest diagnostics?▼

You should defer to backend ingest diagnostics when the profiler agent is healthy but profiles are still not appearing. This Skill explicitly hands off to backend troubleshooting when symptoms indicate the failure is downstream rather than within the agent-side DaemonSet.

Do I need Helm to diagnose a failing GPU profiler agent in a Kubernetes cluster?▼

You need Helm to diagnose a failing GPU profiler agent because this Skill validates the Helm release presence and checks DaemonSet health. It uses kubectl and Helm workflows to triage GPU versus CPU expectations and container configuration mismatches.

Related Skills

Explore More Software Engineering Skills→
phuetzphuetz
30

kubernetes

Consolidate kubectl, Helm, and ArgoCD workflows for Kubernetes cluster administration.

Community
Advanced
zystem-iozystem-io
5

troubleshoot-zymtrace-backend

Diagnose zymtrace backend ingest pipeline failures using helm and kubectl logs.

Official
Advanced
grafanagrafana
31

relatedmetrics

Identify related metric relationships within Grafana Metrics Drilldown.

Official
Advanced
infantesromeroadrianinfantesromeroadrian

pentest-container-breakout

Analyze container and Kubernetes breakout techniques for offensive security operations.

Community
Advanced