358 个 · 按相关度排序
Configure OpenTelemetry to send AI application traces, records of execution steps, to Confident AI. Reuse existing exporters, choose the regional endpoint, and add AI-specific attributes without requiring the deepeval Python package.
中文简介正在准备中。当前显示英语简介。
Install and configure WizTelemetry Platform Service, the shared API backend for KubeSphere observability extensions. Generate configuration based on installed extensions, update installation settings, and inspect service health, pods, and logs.
中文简介正在准备中。当前显示英语简介。
Use this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is installed — defining a doca_telemetry_exporter_schema and event types, creating sources, picking a publish surface (typed events / opaque events / the metrics counter-gauge-histogram API / OTLP logs / NetFlow), walking the schema-then-source lifecycle, or debugging DOCA_ERROR_* failures from the exporter API. Trigger even when the user does not explicitly mention "DOCA Telemetry Exporter" or "doca_telemetry_exporter_*" — typical implicit phrasings include "publishing counters from my DOCA app", "BAD_STATE when I report an event", "consumer/DTS sees nothing but my report succeeded", "how do I export NetFlow/IPFIX records", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service (DTS), plain stdout logging via doca_log, or real-time event subscription back into the app via doca-comch — those belong to other skills.
中文简介正在准备中。当前显示原文说明。
doca_telemetry_utils command line on a host with DOCA: discover the diagnostic-counter schema, translate counter names to binary Data IDs and back, and check per-device counter support before committing a DOCA Telemetry exporter config. Start here when telemetry counters vanish between the exporter and the collector: "my exporter ships but the collector sees nothing", "this metric silently drops downstream", "which counters does this BlueField expose", "translate this 0x... back to a counter name", "what do node / pcie_index / depth mean here", or "is this counter supported on this device", even without naming the tool. Writing exporter or collector code belongs to doca-telemetry-exporter / doca-telemetry; DTS deployment to doca-dts; DOCA install or repair to doca-setup.
中文简介正在准备中。当前显示原文说明。
Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {ship counters to Fluent Bit from the DPU}, {daemon starts but no schema rows appear}. This skill owns the CollectX collection mechanism plus the operator's own doca-telemetry / doca-telemetry-exporter usage; it ROUTES the productized DOCA Telemetry Service (DTS) to public docs (AGENTS.md Non-goal #7), the reader API to doca-telemetry, and the publisher API to doca-telemetry-exporter. Refuse to invent clx symbols, provider names, schema fields, flags, or config paths — describe the class and route to the live source.
中文简介正在准备中。当前显示原文说明。
Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of pcf telemetry or its usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
中文简介正在准备中。当前显示原文说明。
Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-pages telemetry or its usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
中文简介正在准备中。当前显示原文说明。
Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of model-apps telemetry or its usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
中文简介正在准备中。当前显示原文说明。
Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-automate telemetry / usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
中文简介正在准备中。当前显示原文说明。
Add Arize AX tracing to an LLM application, recording how model calls and tool executions connect. Inspect the existing code, select suitable integrations, add instrumentation, and verify that the application runs and traces reach Arize.
中文简介正在准备中。当前显示英语简介。
Set up distributed tracing in KubeSphere to follow requests across services. Covers extension installation, trace collection, automatic application instrumentation, and API queries for traces, individual processing steps, and service connections.
中文简介正在准备中。当前显示英语简介。
Install and configure WizTelemetry Logging in KubeSphere to collect container output and file logs. Use its API to filter logs by workload, time, or keywords, retrieve statistics, and export results.
中文简介正在准备中。当前显示英语简介。
Set up WizTelemetry Ruler in KubeSphere to generate alerts from events, audit records, and container logs. Manage alert rules, configure notification destinations, and query alert history or statistics by time range, severity, and other filters.
中文简介正在准备中。当前显示英语简介。
Set up WizTelemetry Auditing to collect Kubernetes and KubeSphere audit events, records of system operations. Configure storage and retention, then query events by user, action, resource, response status, or time.
中文简介正在准备中。当前显示英语简介。
Use this skill to read DOCA hardware-counter events from a `doca_dev` through the per-domain Telemetry reader libraries: `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, and `_pci`. It covers capability checks, context creation, startup, and per-domain reads or samples. Trigger for implicit requests such as "read PCC counters from my BlueField app", "sample DPA counter exports", or "expose PHY, PCI, or DIAG counters from this doca_dev". This is the counter-reader surface, not a NetFlow, IPFIX, or local-socket collector. Route publishing and export to `doca-telemetry-exporter`; route the deployed DOCA Telemetry Service to `doca-dts`, and collectors and plain stdout logging elsewhere.
中文简介正在准备中。当前显示原文说明。
Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of mobile-app usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
中文简介正在准备中。当前显示原文说明。
Create Terraform files that define alerts for AI agent latency, errors, token use, safety, security, and response quality. Check telemetry and existing policies first, then validate the generated configuration. Quality alerts require Vertex AI.
中文简介正在准备中。当前显示英语简介。
Set up WizTelemetry Events to collect and store Kubernetes events in KubeSphere. Configure index retention policies and use the query API to filter warnings, inspect resource events, generate statistics, or export matching records.
中文简介正在准备中。当前显示英语简介。
Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights. Triggers: "AzureMonitorExporter java", "opentelemetry azure java", "application insights java otel", "azure monitor tracing java". Note: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.
中文简介正在准备中。当前显示原文说明。
Internal — for Boundless team members only. Query Boundless broker telemetry tables on Redshift for prod/staging operational data. Use when the user asks about broker health, request evaluations, request completions, proving times, skip rates, telemetry data, or wants to run SQL against the telemetry database on live networks. Also covers historical telemetry through 2026-04-24 stored as Parquet archives in S3 (queried via DuckDB). Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.
中文简介正在准备中。当前显示原文说明。
Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.
中文简介正在准备中。当前显示原文说明。
Retrieve BigQuery execution records and resource metrics using the right tool for each task. The skill guides monitoring tool selection and SQL queries for performance investigations, capacity analysis, and reviews of billable compute and storage usage.
中文简介正在准备中。当前显示英语简介。
Record and query iii engine logs, traces that show how calls flow, and operational metrics. Set up reactions to incoming errors, inspect alerts, and review metrics aggregated over time windows.
中文简介正在准备中。当前显示英语简介。
Set up KubeSphere’s WizTelemetry Data Pipeline to collect, transform, and route logs, audit data, events, and notifications. Configure delivery to OpenSearch, deploy agents across selected clusters, and check their operating status.
中文简介正在准备中。当前显示英语简介。