
Wiztelemetry Tracing
Use when working with WizTelemetry Tracing extension for KubeSphere, including...
Install
npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -g -a claude-code -y- Repository
- kubesphere/kubesphere17.1k
- Category
- Engineering
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API
WizTelemetry Tracing
Overview
WizTelemetry Tracing is an extension component in the KubeSphere Observability Platform that provides distributed tracing functionality based on the OpenTelemetry 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
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
