[juniper_srx] extract IP from RPD_IFD_NOTIFICATION events#18927
Draft
[juniper_srx] extract IP from RPD_IFD_NOTIFICATION events#18927
Conversation
Add a tag-specific grok in the system pipeline to extract the interface address from RPD_IFD_NOTIFICATION messages (pattern: "address #N <IP>") into host.ip and related.ip. Declare juniper.srx.system.if_trace and juniper.srx.interface_index fields surfaced by the message k-v extractor. Also avoid overwriting an already-populated message field when renaming juniper.srx.message. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
✅ Vale Linting ResultsNo 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 |
💚 Build Succeeded
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
grokin thesystempipeline to extract the interface address fromRPD_IFD_NOTIFICATIONmessages (patternaddress #N <IP>) intohost.ipandrelated.ip.juniper.srx.system.if_traceandjuniper.srx.interface_indexfields, which the existingjuniper.srx.system.*k-v extractor surfaces from these events.juniper.srx.message→messagerename to avoid overwriting an already-populatedmessagefield.1.28.0and add a changelog entry. (Note: the changelog link references PR [juniper_srx] extract IP from RPD_IFD_NOTIFICATION events #18927 as a placeholder; please update it to the actual PR number after creation.)Test plan
elastic-package test pipeline -C packages/juniper_srx --data-streams log— all 14 cases PASS.RPD_IFD_NOTIFICATIONtest event intest-system.logproduceshost.ip: ["175.16.199.0"]andrelated.ip: ["175.16.199.0"].elastic-package check -C packages/juniper_srxpasses (lint + build, README regenerated).🤖 Generated with Claude Code