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.

Sign up for GitHub

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

Jump to bottom

[Security Solution] Cypress: set a large default rule interval #153689

Open
Tracked by #161505
banderror opened this issue Mar 24, 2023 · 2 comments
Open
Tracked by #161505

[Security Solution] Cypress: set a large default rule interval #153689

banderror opened this issue Mar 24, 2023 · 2 comments
Labels
performance Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture test_ui_functional test

Comments

@banderror
Copy link
Contributor

Epic: #153633
Related to: comment

Summary

By default, all rules in Cypress and API integration tests should run with a large enough interval, so that they execute only once during the test run and don't create extra load on Kibana in the test environment.

There may be exceptions to this rule, for example, tests checking subsequent rule runs (e.g. tests for the New Terms rule type) might need to run a rule multiple times during the same test, this is where a test might need a short rule interval.

Example of a default rule interval: 1 day.
@banderror banderror added test performance test_ui_functional technical debt Improvement of the software architecture and operational architecture Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team 8.8 candidate labels Mar 24, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

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

This was referenced Mar 24, 2023
Open
Open
@banderror banderror self-assigned this Mar 27, 2023
@banderror banderror removed their assignment May 16, 2023
@banderror banderror mentioned this issue Jul 8, 2023
Open
@VidhiRambhia VidhiRambhia mentioned this issue Nov 23, 2023
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture test_ui_functional test
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@banderror @elasticmachine