[hpe_aruba_cx] Fix PROC_ID grok pattern to allow optional colon after PID bracket - #20765
Conversation
… PID bracket Some ArubaOS-CX switches emit a space instead of ]: after the process ID, causing 100% parse failures. Making the colon optional fixes parsing for both variants while remaining backward compatible. Closes elastic#18867 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🚀 Benchmarks reportTo see the full report comment with |
qcorporation
left a comment
There was a problem hiding this comment.
@mjwolf can we do something about the suricata changes? the vera-bot also has called this out.
I've taken out those unintentional changes |
|
✅ All changelog entries have the correct PR link. |
|
🟢 No issues across the latest commits 18498cd…cadad75 (16 commits). Review summaryIssues found across earlier commits 13f7418…3d6e3fe (21 commits) — 1 criticalPackage-level:
Issues found across earlier commits a94d11f — 1 low
Issues found across earlier commits ace4d78 — 1 low
🤖 AI-Generated Review | Vera Review Bot - v0.2.6 | 📚 Knowledge base: integration-skills
|
💚 Build Succeeded
History
|
|
Package hpe_aruba_cx - 0.4.5 containing this change is available at https://epr.elastic.co/package/hpe_aruba_cx/0.4.5/ |
Proposed commit message
Some ArubaOS-CX switches emit a space instead of ]: after the process ID, causing 100% parse failures. Making the colon optional fixes parsing for both variants while remaining backward compatible.
Checklist
changelog.ymlfile.Related issues