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.
Where does wiztelemetry-tracing live?
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Which agents can use wiztelemetry-tracing?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Use when working with WizTelemetry Tracing extension for KubeSphere, including installation, configuration, and tracing query API
name: wiztelemetry-tracing
description: 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
This outputs the latest version (e.g., 1.0.6). Note this down - you'll use it in the InstallPlan.
Step 3: Get Generator Endpoint
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.
Step 4: Confirm Configuration with User
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.
Step 5: Create InstallPlan
CRITICAL: InstallPlan metadata.name MUST be wiztelemetry-tracing. DO NOT use any other name.
CRITICAL: config field is YAML format. You MUST:
Use the config structure exactly as shown in the template
DO NOT add configuration fields that are not shown in the template
DO NOT modify the structure or hierarchy
CRITICAL: All placeholders MUST be replaced with actual values. DO NOT leave them as placeholders.
To 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.
Enable Demo
To enable the OpenTelemetry Demo (generates sample trace data), set demo.enabled: true in the config.
Send Traces to Tempo
To forward traces to Tempo instead of OpenSearch, modify the collector.collector.config:
shardCount must match the number of endpoints in global.generator.endpoints.
The nodePort of each shard increases in sequence starting from the configured service.nodePort.
Configuration Parameters
Global Parameters
DNS Service
Parameter
Type
Default
Description
global.dnsService
string
coredns
DNS service name
Generator Global Parameters
Parameter
Type
Default
Description
global.generator.endpoints
list
["http://<ip>:32318"]
Endpoints of all generator shards. Tracing data is routed to different shards by traceId.
OpenSearch Storage Parameters
Parameter
Type
Default
Description
global.storage.opensearch.auth.strategy
string
basic
Auth strategy
global.storage.opensearch.auth.user
string
admin
OpenSearch username
global.storage.opensearch.auth.password
string
admin
OpenSearch password
global.storage.opensearch.endpoints
list
OpenSearch endpoint URLs
global.storage.opensearch.index.prefix
string
wiz-tracing-span
Index prefix
global.storage.opensearch.index.timestring
string
%Y.%m.%d
Index time format (strftime pattern)
Generator Parameters
Parameter
Type
Default
Description
generator.shardCount
int
1
Number of generator shards. Must equal the number of entries in global.generator.endpoints.
generator.image.tag
string
v1.0.2
Generator image tag
generator.image.imagePullPolicy
string
IfNotPresent
Image pull policy
generator.service.nodePort
int
32318
NodePort of the first shard. Subsequent shards use consecutive ports.
"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 inject
Extension Operations
Check Extension Status
kubectl get installplan wiztelemetry-tracing
kubectl get extensions wiztelemetry-tracing
Check Component Status
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 Extension
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
How do I install wiztelemetry-tracing?
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.
Where does wiztelemetry-tracing live?
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Which agents can use wiztelemetry-tracing?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.