[Cisco Ise] Correct guest pipeline to process guest user names - #18107
Conversation
…nstream processors, and added missing generated tags
robester0403
added
Integration:cisco_ise
robester0403
changed the title
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
🚀 Benchmarks reportTo see the full report comment with |
robester0403
changed the title
| # newer versions go on top | ||
| - version: "1.32.2" | ||
| changes: | ||
| - description: Fixed processing issue in guest pipeline for guestuser name. |
There was a problem hiding this comment.
Minor wording typo in the changelog entry: guestuser name should likely be guest user name for readability and consistency in release notes.
| tag: rename_cisco_ise_log_log_details_UserName_to_user_name_d9fe4749 | ||
| field: cisco_ise.log.log_details.UserName | ||
| target_field: user.name | ||
| if: ctx.user?.name == null |
There was a problem hiding this comment.
cisco_ise.log.guest.user.name is populated before the fallback rename from log_details.UserName, so when only UserName is present, user.name gets set later but cisco_ise.log.guest.user.name remains unset. Consider moving the set ... copy_from: user.name step after this fallback rename (or adding a second conditional set) so both username variants consistently populate the guest user field.
💚 Build Succeeded
History
|
|
Package cisco_ise - 1.32.2 containing this change is available at https://epr.elastic.co/package/cisco_ise/1.32.2/ |
3 participants
Proposed commit message
Fix the processing of guest usernames in guest pipelines
Checklist
changelog.ymlfile.- [ ] I have verified that Kibana version constraints are current according to guidelines.- [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practices