- name
Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill wiztelemetry-tracing -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/kubesphere/kubesphere/tree/HEAD/skills/wiztelemetry-tracingFrom the publisher
WizTelemetry Tracing is an extension component in the KubeSphere Observability Platform that provides distributed tracing functionality based on the OpenTelemetry standard.
REQUIRED: Complete all steps in order before generating InstallPlan.
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
Ask user (if not specified):
Available clusters: host, dev
Which clusters do you want to deploy WizTelemetry Tracing to?
MUST do this to get the latest version:
kubectl get extensionversions -n kubesphere-system -l kubesphere.io/extension-ref=wiztelemetry-tracing -o jsonpath='{range .items[*]}{.spec.version}{"\n"}{end}' | sort -V | tail -1
This outputs the latest version (e.g., 1.0.6). Note this down - you'll use it in the InstallPlan.
Get a node IP from the target cluster:
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}'
This outputs a node IP (e.g., 192.168.1.100). Use this as the generator endpoint.
If multiple shards (e.g., generator.shardCount: 3), generate all endpoints:
NODE_IP="<NODE_IP>"
for i in 0 1 2; do
PORT=$((32318 + i))
echo " - http://${NODE_IP}:${PORT}"
done
Replace <NODE_IP> with the actual node IP from the previous command.
Before creating the InstallPlan, confirm the following with the user:
I'll install WizTelemetry Tracing with the following configuration:
- Version: <VERSION>
- Target clusters: <TARGET_CLUSTERS>
- Generator endpoint: http://<NODE_IP>:32318
- OpenSearch endpoint: <OPENSEARCH_ENDPOINT>
Do you want to proceed? (yes/no)
If user confirms, proceed to create the InstallPlan. If not, adjust the configuration based on user feedback.
CRITICAL: InstallPlan metadata.name MUST be wiztelemetry-tracing. DO NOT use any other name.
CRITICAL: config field is YAML format. You MUST:
CRITICAL: All placeholders MUST be replaced with actual values. DO NOT leave them as placeholders.
Based on your selections:
https://opensearch-cluster-data.kubesphere-logging-system.svc:9200)admin)apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: wiztelemetry-tracing
namespace: kubesphere-system
spec:
extension:
name: wiztelemetry-tracing
version: <VERSION> # From Step 2
enabled: true
upgradeStrategy: Manual
config: |
global:
generator:
endpoints:
- http://<HOST_NODE_IP>:32318
storage:
opensearch:
auth:
strategy: basic
user: <OPENSEARCH_USER>
password: <OPENSEARCH_PASSWORD>
endpoints:
- <OPENSEARCH_ENDPOINT>
generator:
shardCount: 1
service:
nodePort: 32318
clusterScheduling:
placement:
clusters:
- <TARGET_CLUSTERS>
Replace placeholders:
<VERSION>: From Step 2 (e.g., 1.0.6)<HOST_NODE_IP>: Node IP from Step 3 (e.g., 192.168.1.100)<OPENSEARCH_USER>: OpenSearch username<OPENSEARCH_PASSWORD>: OpenSearch password<OPENSEARCH_ENDPOINT>: OpenSearch endpoint (e.g., https://opensearch-cluster-data.kubesphere-logging-system.svc:9200)<TARGET_CLUSTERS>: User-confirmed cluster namesTo enable tracing data collection from local log files, set agent.enabled: true in the config. This deploys a DaemonSet that scans log files and forwards traces to the generator.
To enable the OpenTelemetry Demo (generates sample trace data), set demo.enabled: true in the config.
To forward traces to Tempo instead of OpenSearch, modify the collector.collector.config:
collector:
enabled: true
collector:
config: |
exporters:
otlp:
endpoint: <TEMPO_DISTRIBUTOR_GRPC_ENDPOINT>
headers:
x-scope-orgid: wiztelemetry-tracing-ks
tls:
insecure: true
service:
pipelines:
traces:
exporters:
- otlp
- otlphttp
To scale the generator for higher throughput, increase generator.shardCount and update global.generator.endpoints:
global:
generator:
endpoints:
- http://<HOST_NODE_IP>:32318
- http://<HOST_NODE_IP>:32319
- http://<HOST_NODE_IP>:32320
generator:
shardCount: 3
service:
nodePort: 32318
shardCountmust match the number of endpoints inglobal.generator.endpoints. The nodePort of each shard increases in sequence starting from the configuredservice.nodePort.
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/traces" \
-H "X-Remote-User: admin" \
-H "Content-Type: application/json" \
-d '{"condition": {}, "limit": 20}'
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/spans" \
-H "X-Remote-User: admin" \
-H "Content-Type: application/json" \
-d '{"condition": {}, "limit": 20}'
curl -X POST "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/servicegraphs" \
-H "X-Remote-User: admin" \
-H "Content-Type: application/json" \
-d '{"condition": {"start": "<START_TIME>", "end": "<END_TIME>"}}'
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/services" \
-H "X-Remote-User: admin"
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/tags" \
-H "X-Remote-User: admin"
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/values?tags=span.kind&limit=100" \
-H "X-Remote-User: admin"
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/histogram?key=<KEY>&kind=1&interval=15m&startTime=<START>&endTime=<END>" \
-H "X-Remote-User: admin"
Query Parameters:
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/workloads?keys=<KEYS>&startTime=<START>&endTime=<END>" \
-H "X-Remote-User: admin"
Query Parameters:
# Get apdex thresholds
curl -X GET "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/apdex/thresholds?keys=<KEYS>" \
-H "X-Remote-User: admin"
# Set apdex thresholds
curl -X PUT "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:80/kapis/tracing.wiztelemetry.io/v1alpha1/apdex/thresholds" \
-H "X-Remote-User: admin" \
-H "Content-Type: application/json" \
-d '{"serviceA:serviceB": 0.5}'
kubectl apply -f - <<EOF
apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
name: my-instrumentation
spec:
exporter:
endpoint: http://wiztelemetry-tracing-collector.wiz-telemetry-tracing:4317
propagators:
- tracecontext
- baggage
- b3
sampler:
type: parentbased_traceidratio
argument: "0.25"
python:
env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://wiztelemetry-tracing-collector.wiz-telemetry-tracing:4318
dotnet:
env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://wiztelemetry-tracing-collector.wiz-telemetry-tracing:4318
go:
env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://wiztelemetry-tracing-collector.wiz-telemetry-tracing:4318
EOF
Add the following annotation to a pod or namespace:
Annotation values:
"true" - inject from the namespace's Instrumentation resource"my-instrumentation" - use a specific Instrumentation CR in the current namespace"my-ns/my-instrumentation" - use an Instrumentation CR in a different namespace"false" - do not injectkubectl get installplan wiztelemetry-tracing
kubectl get extensions wiztelemetry-tracing
kubectl get statefulset -n wiz-telemetry-tracing
kubectl get deployment -n wiz-telemetry-tracing
kubectl get daemonset -n wiz-telemetry-tracing
kubectl get pods -n wiz-telemetry-tracing
Uninstall from all clusters:
kubectl delete installplan wiztelemetry-tracing
Uninstall from specific cluster:
To remove WizTelemetry Tracing from a specific cluster, update the InstallPlan by removing that cluster from clusterScheduling.placement.clusters:
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: wiztelemetry-tracing
spec:
extension:
name: wiztelemetry-tracing
version: <VERSION>
enabled: true
upgradeStrategy: Manual
clusterScheduling:
placement:
clusters:
- <REMAINING_CLUSTERS> # Remove the cluster you want to uninstall from
© 2026 Skills Rack.
---name: wiztelemetry-tracingdescription: Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration…---# skills/wiztelemetry-tracing/SKILL.mdFAQ
Download skills/wiztelemetry-tracing/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
| string |
2000Mi |
| Vector sidecar memory limit |
agent.vector.resources.requests.cpu | string | 100m | Vector sidecar CPU request |
agent.vector.resources.requests.memory | string | 100Mi | Vector sidecar memory request |