Skip to content
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

Analyzer does not include indices to use in requests #89337

Closed
jonathan-buttner opened this issue Jan 26, 2021 · 2 comments · Fixed by #90727
Closed

Analyzer does not include indices to use in requests #89337

jonathan-buttner opened this issue Jan 26, 2021 · 2 comments · Fixed by #90727
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Threat Hunting Security Solution Threat Hunting Team v7.11.1

Comments

@jonathan-buttner
Copy link
Contributor

jonathan-buttner commented Jan 26, 2021

Kibana version:
7.11

Describe the bug:
When viewing the graphical analyzer view for a process graph, the UI does not populate the indices field of the request to the backend. I believe this causes the backend to query all local indices in ES. This fails for CCS where the events are not located on the local ES instance.

Steps to reproduce:
Open the analyzer and observe the network requests in the developer tools.

Expected behavior:
indexPatterns is populated with the same values as the /tree API request.

Screenshots (if relevant):

/tree request has the correct values

image

Notice that the /events API's indexPatterns is an empty array.

image

Other context:
I believe the issue is that this selector is being called:
https://github.com/elastic/kibana/blob/master/x-pack/plugins/security_solution/public/resolver/store/data/selectors.ts#L289

which returns null after the /tree API has returned. A new selector likely needs to be created to return the appropriate parameters depending on the state of the /tree request.

@jonathan-buttner jonathan-buttner added bug Fixes for quality problems that affect the customer experience triaged v7.11.0 Team:Threat Hunting Security Solution Threat Hunting Team labels Jan 26, 2021
@elasticmachine
Copy link
Contributor

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

@jonathan-buttner
Copy link
Contributor Author

cc: @aarju

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Threat Hunting Security Solution Threat Hunting Team v7.11.1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants