← ClaudeAtlas

logdet-difflisted

Compares two logs, before and after a deploy or between two environments, and lists the new, vanished, spiking and quieter failure signatures with counts and rates, so a regression shows up as a short list instead of a pile of lines. Use when the user says "what changed after the deploy", "diff these two logs", "compare staging and production logs", "did the release add new errors", "is this error new", or "what got worse since yesterday".
vivekbhange-hub/log-detective-skill · ★ 0 · Code & Development · score 75
Install: claude install-skill vivekbhange-hub/log-detective-skill
# logdet-diff: what is different in the logs since the change The question after a release is not "what is in the log" but "what is in it now that was not there before". `log_cluster.py --baseline` clusters the new log, matches every signature against the old one and marks it NEW, SPIKING, STEADY or DOWN, and lists what vanished. ## Inputs - The "after" log (the deploy, the new environment) and the "before" log (the baseline). Ideally comparable: similar traffic, similar duration, same service, same level of logging. - Optional: the level to compare (`--level error` is the usual start). - Commands below say `python3`; on Windows use `python` (or `py -3`). ## Outputs - `logs-triage/diff.md`: the table of clusters with status, counts before and after, samples, and the vanished list. - In chat: new error-level signatures first, then spikes, then vanished ones that matter, and a verdict on whether the change looks safe, with its caveats. ## Steps 1. **Confirm authorization.** Both logs must come from systems the user owns or may analyse. 2. **Check the two logs are comparable.** Ask how long each covers and whether traffic was similar. A 10-minute baseline against a 3-hour "after" log inflates nothing (the comparison uses per-minute rates), but a quiet baseline against a peak-hour log can invent spikes. 3. **Run the comparison:** ``` python3 "${CLAUDE_SKILL_DIR}/../logdet-triage/log_cluster.py" after.log \ --baseline before.log --level warning --re