Skill Detail

Query HyperDX logs, traces, metrics, and session replay from agent incident workflows

Use HyperDX and its agent-friendly CLI output to search, live-tail, and correlate OpenTelemetry signals during supervised production investigations.

Monitoring & AlertsMulti-Framework
Monitoring & Alerts Multi-Framework Security Reviewed
⭐ 9.9k GitHub stars ⬇ 2.4k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill query-hyperdx-logs-traces-and-session-replay-from-agent-incident-workflows Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
HyperDX, OpenTelemetry instrumentation or collector, ClickHouse-backed deployment, optional @hyperdx/cli
Install & setup
Deploy HyperDX using the upstream quickstart or Docker Compose path, point OpenTelemetry SDKs or collectors at the HyperDX collector endpoint, then optionally install the CLI with npm install -g @hyperdx/cli for terminal search, live tail, SQL, NDJSON, and dashboard output.
Author
HyperDX
Publisher
Organization
Last updated
Sep 20, 2026
Quick brief

Use HyperDX when an agent is helping an operator investigate a production issue across logs, traces, metrics, errors, and session replay. The agent can use the documented OpenTelemetry setup and HyperDX CLI/TUI paths to search recent events, live-tail telemetry, inspect trace waterfalls, render terminal dashboards, or consume raw SQL/NDJSON output for a written incident summary. Invoke this instead of normal product usage when the task is a repeatable terminal or scripted incident workflow with evidence capture. The scope boundary is observability investigation on HyperDX data; it is not a generic ClickHouse listing, generic dashboard listing, or broad application monitoring platform card.

How it works

What this skill actually does

Inputs and prerequisites: HyperDX, OpenTelemetry instrumentation or collector, ClickHouse-backed deployment, optional @hyperdx/cli.

Setup notes: Deploy HyperDX using the upstream quickstart or Docker Compose path, point OpenTelemetry SDKs or collectors at the HyperDX collector endpoint, then optionally install the CLI with npm install -g @hyperdx/cli for terminal search, live tail, SQL, NDJSON, and dashboard output.

Source and verification boundary: use https://hyperdx.io/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.