sentinel_one: fix unified alert parent process name mapping - #19513
Conversation
✅ 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 |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
navnit-elastic
left a comment
There was a problem hiding this comment.
Please update the latest_unified_alert transform destination to declare process.parent.name. Also bump fleet_transform_version.
| "type_value": "STATIC", | ||
| "uid": "analytic-uid-001" | ||
| }, | ||
| "assets": [ |
There was a problem hiding this comment.
I believe the structural changes (from arrays to objects) are introduced due to stack version change. However, the pipeline test expected output still uses the array shapes. Recommend regenerating the sample event against a minimum stack version to preserves array shapes.
The unified alert pipeline incorrectly mapped the GraphQL parentName field to process.parent.command_line instead of process.parent.name. parentName contains the process name (e.g. "curl"), not a full command line.
|
✅ All changelog entries have the correct PR link. |
��� Build Succeeded
History
cc @efd6 |
|
Package sentinel_one - 2.8.1 containing this change is available at https://epr.elastic.co/package/sentinel_one/2.8.1/ |
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots