hyperdx

Query HyperDX logs and traces with Lucene syntax via a bundled CLI script.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/LunarCommand/claude-skills --skill hyperdx-lunarcommand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyperdx
Source: https://github.com/LunarCommand/claude-skills/tree/main/skills/hyperdx
Command: npx skills add https://github.com/LunarCommand/claude-skills --skill hyperdx-lunarcommand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, docker, and includes scripts (resource) components.

What problem does it solve? Debugging a misbehaving service usually means digging through observability dashboards by hand. This Skill lets you query HyperDX logs and traces directly from your AI session using Lucene syntax, against either the HyperDX cloud API or a local ClickHouse instance running in Docker. ## Core Features & Use Cases - Dual-mode querying: Search the HyperDX cloud REST API with a Personal API key, or query a local HyperDX container's ClickHouse directly via docker exec. - Lucene query support: Use field filters like level:error, service:name, and TraceId lookups, plus free-text search, with multiple --query terms automatically OR'd together. - Trace inspection: Switch to the traces table in local mode to inspect spans, durations, and status codes for distributed tracing. - Use Case: A user notices elevated 500 errors on their API. They ask the assistant to check the logs, and the Skill runs hdx_query.sh with level:error filtered to their service over the last 30 minutes, then summarizes the repeated error patterns. ## Quick Start Ask the assistant to check HyperDX for recent errors on your service, for example: show me any level:error logs from the api service in the last 15 minutes.

Frequently Asked Questions about hyperdx

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

FAQPage Schema
How do I query HyperDX logs from the command line?

Run the bundled hdx_query.sh script with one or more --query flags containing Lucene terms, such as hdx_query.sh -k your-key -s your-service -q "level:error". Multiple --query flags are OR'd together automatically, and you can adjust the time window with --minutes and result count with --limit.

How do I search logs across multiple services in HyperDX?

Omit the --service flag to sweep all services, or define per-service keys like OTEL_SERVICE_NAME_API in .agent.env and pass the matching one with -s. The script filters by ServiceName when a service is provided.

Can I query a local HyperDX instance instead of the cloud API?

Yes, local mode queries ClickHouse directly inside your HyperDX Docker container. Set HYPERDX_MODE to local in .agent.env, then the script runs with --local and --container flags, using docker exec instead of the REST API. Docker must be installed.

Why does my HyperDX query return Unauthorized errors?

An Unauthorized error means you are using the wrong API key type. HyperDX requires the Personal API Key from your account settings, not the Ingestion API Key. Update HYPERDX_LOCAL_API_KEY in your .agent.env file with the correct key.

Why does a local HyperDX query return no results for level:WARN?

Local mode matches field values exactly and case-sensitively, and SeverityText is stored lowercase. Use level:warn, level:error, or level:info instead of uppercase variants, or drop the filter and grep the Body field with free text.