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

[Security Solution] - Fail to create EQL rule when courier:maxConcurrentShardRequests is set #165090

Open
fdartayre opened this issue Aug 29, 2023 · 7 comments
Labels
bug Fixes for quality problems that affect the customer experience consider-next Feature:Event Correlation (EQL) Rule Security Solution Event Correlation (EQL) rule type impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@fdartayre
Copy link

Kibana version: 8.9.1

Describe the bug:

Creating an EQL rule after configuring courier:maxConcurrentShardRequests in the Advanced Settings of the Space results in the following error:

{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "request [/kibana_sample_data_logs/_eql/search] contains unrecognized parameter: [max_concurrent_shard_requests]"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "request [/kibana_sample_data_logs/_eql/search] contains unrecognized parameter: [max_concurrent_shard_requests]"
  },
  "status": 400
}

Steps to reproduce:

Screenshot 2023-08-29 at 15 08 11
@fdartayre fdartayre added bug Fixes for quality problems that affect the customer experience Feature:Event Correlation (EQL) Rule Security Solution Event Correlation (EQL) rule type labels Aug 29, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 29, 2023
@jsanz jsanz added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Aug 31, 2023
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Aug 31, 2023
@MadameSheema MadameSheema added triage_needed Team:Detections and Resp Security Detection Response Team Team:Detection Engine Security Solution Detection Engine Area labels Aug 31, 2023
@elasticmachine
Copy link
Contributor

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

@yctercero
Copy link
Contributor

Hey @astefan ! Could you confirm that this is expected behavior?

@fdartayre this seems more a product of the language implementation. If that's the case and not expected behavior (in other words, this should be supported) then I think we can assign this over to Elasticsearch.

On our end we could provide a better error message indicating to the user that this advanced setting is not supported.

@astefan
Copy link

astefan commented Sep 8, 2023

@yctercero ES EQL doesn't support such a parameter. For the record, this is the list of request body parameters recognized by ES SQL: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/eql-search-api.html
When it comes to URL parameters, I believe filter_path is the only one supported: https://www.elastic.co/guide/en/elasticsearch/reference/master/eql.html

@yctercero
Copy link
Contributor

@paulewing not sure how common this scenario is? If you think it's fairly common, we could look at providing a user with a warning that this setting is incompatible with EQL/ESQL rules.

@yctercero yctercero removed their assignment Jun 5, 2024
@pborgonovi
Copy link
Contributor

HI @paulewing
I was revisiting this issue and was able to reproduce and check the same error is still shown to the user.
When you have a time, would you give us an update regarding Yara's question above?

Screenshot 2024-08-02 at 11 09 27 AM Screenshot 2024-08-02 at 11 10 11 AM Screenshot 2024-08-02 at 11 10 20 AM

@yctercero
Copy link
Contributor

@approksiu forwarding this one over to you, if that's ok. Could you take a look? #165090 (comment)

@yctercero yctercero added the impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. label Sep 28, 2024
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 consider-next Feature:Event Correlation (EQL) Rule Security Solution Event Correlation (EQL) rule type impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

No branches or pull requests

7 participants