-
Notifications
You must be signed in to change notification settings - Fork 43
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
[BUG] Group by resources unable to show resources / findings #160
Comments
@tehilashn @kfirpeled I have added this to our last-mile epic with a priority 0 |
This is happening due to the recent changes that were merged roughly at the same:
The queries for the findings-grouped-by-resource table rely on |
Checkout https://github.com/elastic/security-team/issues/3737 for more information of planned work on the findings mapping |
@kfirpeled Since elastic/kibana#132529 (comment) is merged we can either close this issue out or keep it open till we add back |
@tinnytintin10 I've updated this ticket to address the cluster id |
Describe the bug
When switching from the group by none view to the group by resource view, Kibana displays
There are no findings
Preconditions
I am running the main branch of Kibana locally with findings data coming from the cloud beat kind-mono cluster.
To Reproduce
Write the exact actions one should perform in order to reproduce the bug.
Steps to reproduce the behavior:
Expected behavior
We should see a resource per row and their associated findings when you click on them.
Screenshots
Screen.Recording.2022-05-19.at.10.58.36.AM.mov
Additional context
The text was updated successfully, but these errors were encountered: