wiztelemetry-tracing
Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API
npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 - **Wi
- Overview
- When to Use
- Components
- Dependencies
- Installation
- Prerequisites
- Enable Agent (Log File Collection)
- Enable Demo
- Send Traces to Tempo
- Multiple Generator Instances
- Configuration Parameters
- Global Parameters
- Generator Parameters
- Operator Parameters
kubectl get clusters -o jsonpath='{.items[*].metadata.name}'
kubectl get nodes -o jsonpath='{.items[0].status.addresses[?(@.type=="ExternalIP")].address}' 2>/dev/null || \
kubectl get nodes -o jsonpath='{.items[0].status.addresses[?(@.type=="InternalIP")].address}'
for i in 0 1 2; do
echo " - http://${NODE_IP}:${PORT}"
done
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/traces" \
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/spans" \
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/servicegraphs" \
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/services" \What does the wiztelemetry-tracing skill do?
Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.