Skip to content

chore: update drain3 default log pattern weights#26164

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

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

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[bot] 👋 — this looks like a well-formed bot-generated retrain of the drain3 default log pattern weights from the train-drain3-weights CI workflow. The change is focused and process-compliant.

One minor note:

  • No test diff included — since this updates weight data consumed at runtime, it's worth verifying there's a schema/schema-validation test that exercises the updated weights file to ensure it parses correctly and the weight values remain within expected bounds.

If you'd like to close this gap, you can assign this prompt to your coding agent:

Check whether there is an existing test that validates the drain3 default log pattern weights
file (the one updated in this PR) parses without errors and contains well-formed entries.
If no such test exists, add a lightweight schema validation test that loads the weights file
and asserts the structure is valid (e.g., all entries have the expected fields and numeric
weight values).

Generated by Contribution Check · ● 1.4M ·

@pelikhan pelikhan closed this Apr 14, 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