Skip to content

chore: update drain3 default log pattern weights#25984

Closed
github-actions[bot] wants to merge 1 commit intomainfrom
ci/train-drain3-weights-20260413
Closed

chore: update drain3 default log pattern weights#25984
github-actions[bot] wants to merge 1 commit intomainfrom
ci/train-drain3-weights-20260413

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This pull request updates the default Drain3 log pattern weights (pkg/agentdrain/data/default_weights.json) by training on the most recent workflow run logs.

What changed

  • Re-trained log template clusters from the latest run logs using gh aw logs --train
  • Copied resulting drain3_weights.json to the embedded defaults path

How to verify

  1. Build the binary with make build
  2. Run gh aw audit or gh aw logs --train and confirm the anomaly analysis reflects the updated patterns

This PR was created automatically by the train-drain3-weights workflow.

@github-actions

This comment has been minimized.

1 similar comment
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown
Contributor Author

Hey @github-actions 👋 — thanks for the automated maintenance update! Refreshing the Drain3 default log pattern weights from the latest training run is exactly the kind of routine upkeep that keeps anomaly detection accurate.

This PR is clean: single file changed, clear description, direct link to the triggering workflow run, and handy verification steps. The CI suite (make build + make test) will exercise the code in pkg/agentdrain/ that consumes default_weights.json, so the existing tests in anomaly_test.go and miner_test.go provide the relevant coverage — no additional test changes are needed for a pure data-file retrain.

⚠️ Soft flag: The contribution checker noted tests: no because the diff touches no _test.go files. This is expected for a weights-only update and should not block merging once CI is green. If any CI check fails on the updated default_weights.json, check whether any assertions in anomaly_test.go or miner_test.go rely on specific cluster IDs or template counts that may have shifted after retraining.

Generated by Contribution Check · ● 3.2M ·

@pelikhan pelikhan closed this Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant