-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security solutions] Fix execution context page #152816
[Security solutions] Fix execution context page #152816
Conversation
edf0d29
to
8447bf2
Compare
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Core review only. LGTM.
Just added a NIT 😇
x-pack/plugins/security_solution/public/common/hooks/use_update_execution_context.ts
Outdated
Show resolved
Hide resolved
8447bf2
to
641346c
Compare
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @machadoum |
## Summary Event Based Telemetry sends context data for each event, for that it uses Kibana `ExecutionContext`. Before this PR events sent from Security Solutions had `context.page` value undefined. ### How to test it 1. Open the browser console and filter for EBT 2. Navigate between pages 3. Check if the click event has the right `context.page` value.
Summary
Event Based Telemetry sends context data for each event, for that it uses Kibana
ExecutionContext
. Before this PR events sent from Security Solutions hadcontext.page
value undefined.How to test it
context.page
value.