Skip to content

docs(kb): suppress noisy messages from the System Logs view#487

Open
CarlRodabaugh wants to merge 1 commit into
mainfrom
docs/kb-suppress-noisy-syslog-messages
Open

docs(kb): suppress noisy messages from the System Logs view#487
CarlRodabaugh wants to merge 1 commit into
mainfrom
docs/kb-suppress-noisy-syslog-messages

Conversation

@CarlRodabaugh

Copy link
Copy Markdown
Collaborator

Summary

New KB article for a recurring support pattern: hardware/driver messages that repeat constantly in System → Logs without indicating a real fault — the classic case being a storage HBA driver logging a failed ioctl on every poll. The article walks through capturing the stable part of the message, building a POSIX ERE pattern, adding it to syslog_regex_list via the API, reloading log capture per node, and verifying in the Logs view.

Type

How-to / Troubleshooting (system logs)

Source

Recurring support pattern. Promoted from internal support KB.

Note for reviewers

The syslog_regex_list setting isn't exposed in System → Settings → Advanced Settings, so the article routes users through System → API Documentation to set it. The central caveat, repeated in the intro and at verification: the filter only hides lines from the UI Logs view — the kernel still writes them, so they stay in the raw syslog inside a sysdiag by design. Verify in the Logs view, not by grepping a sysdiag.

Checks

  • validate_frontmatter.py passes locally
  • Internal links point at existing product-guide pages (advanced-system-settings, node-diagnostics)

🤖 Generated with Claude Code

Add a KB article for a recurring support pattern: hardware/driver
messages that repeat in System -> Logs without indicating a real fault
(e.g. an HBA driver logging a failed ioctl on every poll). Covers
capturing the stable message text, building a POSIX ERE pattern, adding
it to syslog_regex_list via the API, reloading log capture per node, and
verifying in the Logs view.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant