issue-109: Add victorialogs-debugging skill #110

Merged

david merged 1 commit from feature/issue-109/add-victorialogs-debugging-skill into main

2026-08-29 02:56:54 +00:00

david commented

2026-08-29 02:52:51 +00:00

Owner

Adds a new victorialogs-debugging skill — a debugging playbook + LogsQL recipe cheat-sheet for working with VictoriaLogs through the victorialogs extension (logs_search, logs_hits, logs_facets). The extension provides the query tools; the skill provides the strategy: three quick-start traces for the three most common debugging questions, a shared gotchas list, and a consolidated LogsQL cheat-sheet.

What & why

Debugging against VictoriaLogs is a recurring need in this repo's workflows, and raw LogsQL has several non-obvious pitfalls (default 15m time window, bare-phrase handling, underscore tokenisation). This skill codifies what was previously tribal knowledge into a repeatable playbook:

Error-spike / incident triage — find when errors started, which services/fields are involved, and drill into a spike with logs_hits.
Known-entity tracing — follow one request/trace/entity through the logs across services.
Missing-log investigation — determine why expected logs aren't showing up (window, field spelling, phrase vs bare term).
Gotchas — the default 15m window, phrase/underscore query pitfalls, and how to widen the time range.
LogsQL cheat-sheet — consolidated reference of the recipes used across the traces.

All recipes were smoke-tested against a real VictoriaLogs instance (v1.52.0 at http://localhost:9428) before shipping.

Per-file breakdown

Added

skills/victorialogs-debugging/SKILL.md — the new skill (frontmatter name: victorialogs-debugging; playbook, traces, gotchas, cheat-sheet).

Modified

README.md — skill count 12→13, new row in the skills table, layout note update.
CHANGELOG.md — Unreleased → Added entry describing the skill.

Closes #109

Adds a new `victorialogs-debugging` skill — a debugging playbook + LogsQL recipe cheat-sheet for working with VictoriaLogs through the `victorialogs` extension (`logs_search`, `logs_hits`, `logs_facets`). The extension provides the query tools; the skill provides the strategy: three quick-start traces for the three most common debugging questions, a shared gotchas list, and a consolidated LogsQL cheat-sheet. ## What & why Debugging against VictoriaLogs is a recurring need in this repo's workflows, and raw LogsQL has several non-obvious pitfalls (default 15m time window, bare-phrase handling, underscore tokenisation). This skill codifies what was previously tribal knowledge into a repeatable playbook: - **Error-spike / incident triage** — find when errors started, which services/fields are involved, and drill into a spike with `logs_hits`. - **Known-entity tracing** — follow one request/trace/entity through the logs across services. - **Missing-log investigation** — determine why expected logs aren't showing up (window, field spelling, phrase vs bare term). - **Gotchas** — the default 15m window, phrase/underscore query pitfalls, and how to widen the time range. - **LogsQL cheat-sheet** — consolidated reference of the recipes used across the traces. All recipes were smoke-tested against a real VictoriaLogs instance (v1.52.0 at `http://localhost:9428`) before shipping. ## Per-file breakdown **Added** - `skills/victorialogs-debugging/SKILL.md` — the new skill (frontmatter `name: victorialogs-debugging`; playbook, traces, gotchas, cheat-sheet). **Modified** - `README.md` — skill count 12→13, new row in the skills table, layout note update. - `CHANGELOG.md` — Unreleased → Added entry describing the skill. Closes #109

david added the

feature

label

2026-08-29 02:52:51 +00:00

david self-assigned this

2026-08-29 02:52:51 +00:00

david added 1 commit

2026-08-29 02:52:52 +00:00