argos-query

Search and analyze Argos service logs by PSM, keyword, logID, or error aggregation.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill argos-query-yuezhen-huang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argos-query
Source: https://github.com/yuezhen-huang/my-bytedance-skillhub/tree/main/argos-query
Command: npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill argos-query-yuezhen-huang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Investigating production issues requires digging through distributed service logs across regions, which is slow and error-prone when done manually. This Skill lets you query Argos logs by service PSM, keyword, logID, or error aggregation through a single command, with built-in guardrails for region selection and time ranges. ## Core Features & Use Cases - Centralized Log Search: Search service logs by PSM with optional keywords, log level filters, and relative time ranges like 1h or 30m. - LogID Tracing: Trace a single request across services using its logID, returning PSM, pod, IP, env, and message details. - Error Aggregation: Summarize top error sources by location with counts and sampled messages instead of reading raw logs. - Local File Inspection: Query PPE or instance-local log files when env, env_type, or path is specified. - Use Case: A user asks "check if my.service.name had timeout errors in the last hour in Singapore" and gets matching log entries with hit counts in one call. ## Quick Start Ask the assistant to search logs for a given PSM in a specific vregion over a recent time range, optionally adding keywords or a logID to trace.

Frequently Asked Questions about argos-query

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

FAQPage Schema
How do I search service logs by keyword in Argos?

Run gdpa-cli with the argos-query agent, passing the psm, a keywords array, vregion, and a time_range such as 1h. You can add log_level to narrow results to a specific severity like Error.

How to trace a request using a logID across services?

Pass the logid parameter with a vregion and optionally scan_span_in_min to control the search-back window. The query returns trace entries including PSM, pod, IP, env, IDC, level, and message for that request.

What should I do when Argos log search returns total 0?

A total of 0 usually means the wrong vregion, env, or time window rather than no logs existing. Confirm the region and scope with the user instead of automatically probing other regions one by one.

Can I query logs across multiple regions at once?

Yes, pass a comma-separated vregion list such as sg,us, but only when the user explicitly requests multi-region results. The output groups hit counts per region in a multi_region response.

When should I use local file mode instead of central search?

Use local file mode for PPE verification or instance-local log inspection by providing env, env_type, or path along with the psm. Central search remains the default for general service log queries.

How do I find the top error locations for a service?

Use error analysis mode by passing the psm with aggregator set to location, plus vregion and time_range. The result lists top code locations with error counts, levels, and sampled messages.