-
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 Solution][Resolver] Show origin node details in panel on load #73313
[Security Solution][Resolver] Show origin node details in panel on load #73313
Conversation
Pinging @elastic/endpoint-app-team (Feature:Resolver) |
Pinging @elastic/endpoint-data-visibility-team (Team:Endpoint Data Visibility) |
useEffectOnce(() => { | ||
return () => cleanUpQueryParams(); | ||
}); | ||
|
||
useEffect(() => { | ||
if (activeDescendantId && crumbId !== activeDescendantId) { |
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.
Went this route because, when you refresh the page after selecting a process in the table view (not the timeline view), the old crumbId is still there in the query string even though you don't see a resolver anymore. This just makes sure everything is in sync on load for that view as well as the timeline
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.
can you put that in a comment? We're probably going to schedule rewriting all query string related stuff soon and i want to have all the expected behavior somewhere
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.
yep, done. Thanks!
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.
❔ This only happens when you refresh
the page (like you hit f5 or something)? There is that event in panel.tsx
called appDetectedNewIdFromQueryParams
- I'm assuming that doesn't fire for whatever reason when you refesh? Followup ❔ - should that action fire here as well?
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.
I also want it to show on the initial load of the resolver. The panel should update with the details for the origin node. When I set it up to only work on initial load, I noticed this issue, and decided to set it up to be more general. This is more of an issue of the resolver that's opened in the table (not the timeline) not being preserved through refresh. That could leave you in a state when you open a new resolver that the activeDescendantID
is set, but the crumbID
isn't set. It doesn't necessarily cause any issues at the moment, but I prefer to be cautious and keep them in sync. In a refactor we should just combine those values in some way since they should always be the same
useEffectOnce(() => { | ||
return () => cleanUpQueryParams(); | ||
}); | ||
|
||
useEffect(() => { | ||
if (activeDescendantId && crumbId !== activeDescendantId) { |
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.
can you put that in a comment? We're probably going to schedule rewriting all query string related stuff soon and i want to have all the expected behavior somewhere
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.
1 ❔
@elasticmachine merge upstream |
💚 Build SucceededBuild metricsasync chunks size
History
To update your PR or re-run it, just comment with: |
…ad (elastic#73313) * show origin node details in panel on load * added comment Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…ad (elastic#73313) * show origin node details in panel on load * added comment Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* master: (44 commits) [Search] add server logs (elastic#72454) [SIEM][Timelines] Updates timeline template callout text (elastic#73334) Fix App status flaky test (elastic#72853) [Functional Tests] Increase the timeout when locating the tableview] (elastic#73243) Use "Apply_filter_trigger" in dashboard drilldown (elastic#71468) fix dashboard index pattern race condition (elastic#72899) [Functional Tests] Increase waitTime for timelion to fetch the results (elastic#73255) [Functional Tests] Fix flakiness on TSVB chart on switching index patterns test (elastic#73238) updates cypress to v4.11.0 (elastic#73327) [Metrics UI] Saved views bugs (elastic#72518) [Ingest Manager] Convert select agent config step to use combo box (elastic#73172) Exclude `version` from package config attributes that are copied, add safeguard to package config bulk create (elastic#73128) [Security Solution][ML] Updates siem group name to security (elastic#73218) [Security Solution] Show proper icon for termination status of all processes (elastic#73235) [Security Solution][Resolver] Show origin node details in panel on load (elastic#73313) [Security solution] Threat hunting test coverage improvements (elastic#73276) [Security Solution][Exceptions] - Update exception item comments to include id (elastic#73129) [Enterprise Search] Error state UI tweaks to account for current Cloud SSO behavior (elastic#73324) [dev/build/docker_generator] convert to typescript (elastic#73339) [APM] Fix focus map link on service map (elastic#73338) ...
Summary
Show origin process details in panel. The gif below shows an initial load and selecting other process nodes unaffected.
Checklist
Delete any items that are not applicable to this PR.
For maintainers