Remove embedded discover
#6120
Assignees
Labels
Comments
New Discover
Components featuresSearch bar
Histogram chart
Data grid
type tDataGridColumn = {
render?: (value: any) => string | React.ReactNode;
} & EuiDataGridColumn;
export const discoverModuleColumns: tDataGridColumn[] = [{
id: 'timestamp',
},
{
id: 'agent.name',
render: (value: string) => { // return any React.ReactNode for the cell
return (
<EuiBadge>{value}</EuiBadge>
)
}
},
{
id: 'rule.description'
},
{
id: 'rule.level'
},
{
id: 'rule.id'
}]
|
6 tasks
|
I will close this issue, because the angularJS routing will be solved in the next stage of the release. |
|
Added pull request to the list of fixes: #6950 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We want to remove the embedded discover and replace it with a more modern component. This will allow us to remove angular as a dependency, improve usability and performance. Also, this will allow us to adapt to the upcoming changes from the upstream OpenSearch related to the new
discover, the changes of the OUI library and others.We use discover in multiple places, the most apparent one is the Events tabs:
But its components are also used to build other visualizations, managing filters and some events. The removal of the
discoverwill require a refactor of these uses.Our strategy will be to create our own component based on the one we already created for the new inventory tab:
Screen.Recording.2023-10-25.at.10.52.34.mov
We will add to the current inventory tab the time filters and the timeline visualization as shown in the
discover.In general our implementation strategy will be to add the necessary changes to make the
discoverredundant, and then, remove it. Also, we don't want to lose functionality, if there are use cases not identified in this issue, discuss them in the comments sections below. We will update the issue body with the conclusion.Functional requirements
As a user, I want to be able to:
Explore data:
Generate reports:
Explore event context:
Non-functional requirements
Implementation restrictions
Plan
Related fixes/features
The text was updated successfully, but these errors were encountered: