query-finelog

Query Finelog logs and telemetry for Iris tasks, workers, and vLLM metrics.

3.2k|266|Updated Mar 22, 2024
One-click install
npx skills add https://github.com/marin-community/marin --skill query-finelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query-finelog
Source: https://github.com/marin-community/marin/tree/main/.agents/skills/query-finelog
Command: npx skills add https://github.com/marin-community/marin --skill query-finelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnosing distributed training and inference issues requires querying Finelog logs and telemetry across federated and regional deployments, but incorrect schema assumptions, counter semantics, or missing forwarded rows lead to wrong conclusions.

Core Features & Use Cases

  • Schema-First Querying: Discover namespaces and schemas with the finelog CLI before writing bounded SQL against confirmed columns.
  • Counter Semantics Handling: Distinguish native delta counters from imported cumulative Prometheus snapshots, applying LAG-based delta calculations with reset handling.
  • Federated vs Regional Diagnosis: Compare hub and regional deployments to detect forwarding delays, missing logs, or incomplete recent rows.
  • Use Case: An engineer investigating Iris task memory usage queries per-attempt memory samples bucketed by half-hour, then cross-checks a regional deployment when hub rows appear incomplete.

Quick Start

Ask the assistant to query Finelog for the memory usage of a specific Iris task over the last day, discovering the schema first and summarizing results by time bucket.

Frequently Asked Questions about query-finelog

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

FAQPage Schema
How do I query Finelog telemetry for Iris tasks?

First discover available namespaces with 'uv run finelog namespaces <deployment>' and confirm columns with 'uv run finelog schema'. Then run bounded SQL via 'uv run finelog query', reading SQL from stdin when the positional argument is omitted.

How to compute rates from cumulative Prometheus counters in SQL?

Imported counters carry source_temporality 'cumulative_snapshot', so use LAG partitioned by the full series identity to compute per-interval deltas and discard reset intervals where value decreases. Native Rigging counters are already deltas and can be summed directly.

Why are recent logs missing from the federated Finelog hub?

Missing hub rows usually indicate cross-cluster forwarding delay. Query the regional deployment with the exact attempt-suffixed log key; if regional rows exist but hub rows do not, forwarding has not completed yet.

Should I query the marin hub or a regional deployment?

Use the marin deployment for the federated view across clusters, and a regional deployment for peer-local truth or recent rows that may not have forwarded yet. Preserve the cluster column until after per-series calculations.

What are the limitations when querying Finelog telemetry?

You must bound the native time key and keep timestamp_ms predicates numeric, and never assert remembered columns without schema discovery. Never reset or change a shared namespace during diagnosis, and report forwarding or retention caveats with results.