[Security solution] [RAC] Add row renderer popover to alert table "reason" field

[machadoum]

Summary

• It displays a popover containing the row renderer when the user clicks on the reason field value.
• It creates a new column renderer (reason_column_renderer.tsx) for the reason field that renders the row renderer on click.
• It passes down the props required for the reason_column_renderer to call row renderer.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)

[mdefazio]

Do we need to include the event render type in the title of the popover? I'm not super knowledgable about how all these differ and how useful that is to know.

[machadoum]

Do we need to include the event render type in the title of the popover? I'm not super knowledgable about how all these differ and how useful that is to know.

I also don't know how useful it would be. The event renderer name column isn't very informative:

Maybe @paulewing can help us with that.

[mdefazio]

The more I think about it, at the very least, I do think we should include a title of 'Event renderer'. When we bring in the view of all these event renderers, we will want that correlation between the two.

I will discuss with @paulewing whether we need a title, but even then, I think it's better to do something like:
Event renderer: {event_renderer_name}.

[mdefazio]

Spoke with @paulewing , let's go with Event renderer: {event_renderer_name} for the popover title

[michaelolo24]

@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[machadoum]

Spoke with @paulewing , let's go with Event renderer: {event_renderer_name} for the popover title

I added a new commit with the title change.

@michaelolo24 The PR is ready for review!

[michaelolo24]

Do we want a default name for the plain renderer? We can do that in a follow up PR, but we should find out

[machadoum]

I am struggling to find a scenario where we would display the plain RowRenderer. I think that it won't be displayed on the alert page.

When I call getRowRenderer and no ronRenderer is found it returns null Instead of returning plainRowRenderer.

I couldn't find any reference to plain_row_renderer.tsx on the code.

Here there is a comment mentioning it but the comment is outdated because plainRowRenderer is not included on defaultRowRenderers

If I am right, we could delete plain_row_renderer.tsx

[jportner]

It looks like Team:Security was mistakenly added, I'll remove it

[michaelolo24]

Thank you for adding tests!

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

[michaelolo24]

can you update this to:

useMemo(() => {
	return rowRenderer && rowRenderer.renderRow({
      browserFields,
      data: ecsData,
      isDraggable: true,
      timelineId,
    });
}, [..deps]);

[michaelolo24]

This really looks great! Tested out a couple different renderers such as auditd and netflow and they worked great. Just a few comments, but nothing blocking! Great job! 💪🏾

[machadoum]

@michaelolo24 Thank you for reviewing the PR 🙇‍♂️

I fixed all issues. Feel free to take a second look.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 7ba2949
• Storybooks Preview
• Documentation Changes

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	2360	2361	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	6.5MB	6.5MB	+6.3KB
timelines	267.6KB	267.7KB	+108.0B
total			+6.4KB

History

• 💚 Build #144731 succeeded c252e78
• 💔 Build #144709 failed 0ead1cc
• 💔 Build #144627 failed 6c7f6be
• 💔 Build #144475 failed f97f934
• 💔 Build #144381 failed c8e5404

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @machadoum

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.