openclaw-gtrace-install

Install or upgrade the OpenClaw OTEL plugin via the GTrace release flow.

9|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/GuanceCloud/openclaw-otel-plugin --skill openclaw-gtrace-install
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-gtrace-install
Source: https://github.com/GuanceCloud/openclaw-otel-plugin/tree/main
Command: npx skills add https://github.com/GuanceCloud/openclaw-otel-plugin --skill openclaw-gtrace-install

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, tar, node, npm, python3, sha256sum, openclaw, and includes scripts (resource) components.

What problem does it solve?

This Skill removes the manual friction of installing or upgrading the OpenClaw OTEL plugin through the GTrace release flow, so an agent can complete setup with the right endpoints, token, version, and tags in one pass.

Core Features & Use Cases

  • GTrace installation path: Always uses the GTrace installer flow with the correct install type and release source.
  • Parameter-driven execution: Reads OSS endpoint, dataway endpoint, token, version, tags, and optional no-config or no-restart flags directly from the user request.
  • Post-install validation: Verifies the plugin directory and OpenClaw configuration, then restarts the gateway when available.
  • Use Case: An operator wants to install the latest plugin build into an existing OpenClaw environment without manually composing installer commands or checking the config layout.

Quick Start

Use the openclaw-gtrace-install skill to install or upgrade the OpenClaw OTEL plugin from your provided OSS endpoint, dataway endpoint, version, token, and tags, then verify the installation and report any failure clearly.

Frequently Asked Questions about openclaw-gtrace-install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the OpenClaw OTEL plugin through the GTrace release flow?

Installing the OpenClaw OTEL plugin via GTrace requires passing explicit OSS endpoints, dataway endpoints, tokens, versions, and tags to a parameterized installer command, which then verifies the installation and restarts the gateway.

What parameters are needed to upgrade an existing OpenClaw OTEL deployment?

Upgrading an OpenClaw OTEL deployment requires specifying the target version, OSS endpoint, dataway endpoint, token, and tags, while optional no-config or no-restart flags control whether existing configurations are reused or the gateway is restarted.

Does the GTrace installer validate the OpenClaw plugin configuration after deployment?

Yes, the GTrace installer validates inputs before execution and verifies the plugin directory alongside the OpenClaw configuration after deployment, confirming installation success and reporting any failures clearly before restarting the gateway.

Can I deploy the OpenClaw OTEL plugin without restarting the gateway?

Yes, you can deploy the OpenClaw OTEL plugin without restarting the gateway by passing the no-restart flag, allowing the installer to complete the plugin setup and configuration validation while skipping the gateway restart phase.

What dependencies are required to run the OpenClaw GTrace installation process?

Running the OpenClaw GTrace installation process requires curl, tar, node, npm, python3, sha256sum, and an existing openclaw environment to execute the scripts and validate the deployment correctly.