-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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] Narrow down indices to match case descriptions #89592
Conversation
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
⏳ Build in-progress, with failures
Failed CI StepsTo update your PR or re-run it, just comment with: |
@elasticmachine merge upstream |
… into integration-defaultindex
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
docValueFields: [], | ||
inspect: false, | ||
wait_for_completion_timeout: '10s', |
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.
Just curious how we settled on the 10s
timeout?
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.
Sometimes the request just takes longer than expected to return. I want to put the timeout long enough to wait until the result comes back so I am able to verify the result.
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 checked the test here: https://github.com/elastic/kibana/blob/master/x-pack/test/api_integration/apis/search/search.ts#L18
They use a very long timeout to avoid returning just partial data, so I do the same here.
@elasticmachine merge upstream |
@elasticmachine merge upstream |
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.
It seems that will do the work!!!
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @angorayc |
…lastic#89592) * update default index to match with description * narrow down indices to match case description * run specific tests * run only security solution's tests * debug users integration test * wait_for_completion_timeout * run only security_solution * add back integration tests * avoid multiple requests * uncomment tests * unskip tests * add smaller mock data for users and uncommon_processes * put test back Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # x-pack/test/api_integration/apis/security_solution/users.ts
…lastic#89592) * update default index to match with description * narrow down indices to match case description * run specific tests * run only security solution's tests * debug users integration test * wait_for_completion_timeout * run only security_solution * add back integration tests * avoid multiple requests * uncomment tests * unskip tests * add smaller mock data for users and uncommon_processes * put test back Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # x-pack/test/api_integration/apis/security_solution/users.ts
…ions (#89592) (#92284) * [Security Solution] Narrow down indices to match case descriptions (#89592) * update default index to match with description * narrow down indices to match case description * run specific tests * run only security solution's tests * debug users integration test * wait_for_completion_timeout * run only security_solution * add back integration tests * avoid multiple requests * uncomment tests * unskip tests * add smaller mock data for users and uncommon_processes * put test back Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # x-pack/test/api_integration/apis/security_solution/users.ts * update mocked users data * update mocked index * update mocked index * update mocked index * update mock data
…ons (#89592) (#92283) * [Security Solution] Narrow down indices to match case descriptions (#89592) * update default index to match with description * narrow down indices to match case description * run specific tests * run only security solution's tests * debug users integration test * wait_for_completion_timeout * run only security_solution * add back integration tests * avoid multiple requests * uncomment tests * unskip tests * add smaller mock data for users and uncommon_processes * put test back Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # x-pack/test/api_integration/apis/security_solution/users.ts * update mocked users data * update mocked index * update mocked index * update mocked index * update mock data * update mock data
Summary
This PR is to fix #87793
Before we put the defaultIndex of requests too broad, sometimes make the tests flaky.
Similar problem happens to other tests, so remove redundant index along here in this PR.
I also extend the timeout for each test to 10s to avoid returning partial data. For this
users
anduncommon_cases
, I create two mock data which are smaller than the original ones they used. This should be able to reduce the query time.