# Wiztelemetry Tracing

Use when working with WizTelemetry Tracing extension for KubeSphere, including...

- Repository: https://github.com/kubesphere/kubesphere (17074 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-07-15
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -g -a claude-code -y`
Codex: `npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -g -a codex -y`
Cursor: `npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -g -a cursor -y`
Gemini CLI: `npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -g -a gemini-cli -y`

## Description

Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# WizTelemetry Tracing

## Overview

WizTelemetry Tracing is an extension component in the KubeSphere Observability Platform that provides distributed tracing functionality based on the [OpenTelemetry](https://opentelemetry.io/docs/specs/otel/trace/) standard.

## When to Use

- Installing or configuring the WizTelemetry Tracing extension
- Understanding tracing architecture (Generator + Operator + Collector + Agent)
- Using the tracing query API to query traces, spans, service graphs
- Configuring OpenTelemetry auto-instrumentation for applications

## Components

| Component | Description | Default Enabled |
|-----------|-------------|-----------------|
| generator | WizTelemetry Tracing Generator: generates service graphs from tracing data (StatefulSet) | true |
| operator | OpenTelemetry Operator: manages OpenTelemetry Collector and auto-instrumentation | true |
| collector | OpenTelemetry Collector for WizTelemetry: receives traces, exports to Vector and OpenSearch | true |
| agent | WizTelemetry Tracing Agent: collects tracing data from local log files (DaemonSet) | false |
| demo | OpenTelemetry Demo: generates sample tracing data for demonstration | false |

## Dependencies

- **WizTelemetry Platform Service** (whizard-telemetry): Required
- **OpenSearch** (opensearch): Required

## Installation

### Prerequisites

**REQUIRED: Complete all steps in order before generating InstallPlan.**

#### Step 1: Get Available Clusters and Confirm Target

**CRITICAL: DO NOT proceed until target clusters are determined.**

**Step 1.1: Get available clusters**

```bash
kubectl get clusters -o jsonpath='{.items[*].metadata.name}'
```

**Step 1.2: Determine target clusters**

- If user **explicitly specified** target clusters in the request -> Use those clusters directly, proceed to Step 2
- If user **did NOT specify** target clusters -> Ask user to confirm which clusters to deploy to, then proceed to Step 2

The rest: https://github.com/kubesphere/kubesphere/blob/HEAD/skills/wiztelemetry-tracing/SKILL.md