Juan Pablo Djeredjian

Hi @dplumlee Thanks for working on this! I have a major doubt related to the `xpack.alerting.rules.run.alerts.max` config setting, and maybe @banderror @marshallmain and @approksiu can chime in from a tech...

@dplumlee Thanks for the explanation! I agree with everything proposed above by you and @banderror. > It shouldn't be possible to set max_signals to a value < MIN_VALUE. Should MIN_VALUE...

Hi @dplumlee. This is not related to this PR but to [the `setup` field PR](https://github.com/elastic/kibana/pull/178131). I just realized that that PR does not remove the `setup` field from the `security-rule`...

@approksiu cc @banderror @nikitaindik @dplumlee @joepeeples `concurrent_searches` and `items_per_search` are not defaultable fields, so when a IM rule is created these fields are not initialised if not passed explicitly. However,...

Hi @rylnd @nkhristinin As preparation for the [Prebuilt Rules Customization Milestone 3](https://github.com/elastic/kibana/issues/174168), we'll be working on making the `concurrent_searches` and `items_per_search` fields of IM rules editable via the UI. Allowing...

Thanks @rylnd! So @dplumlee, let's ping @approksiu and @ARWNightingale for their approval here: based on Ryland's comment, we would add edit capability to these two features **without** setting a max...

We should have some product input here @approksiu. We can discuss this in the next Simplified Protections meeting, but for context: - We need to make this two fields editable...

Closing ticket after discussion with @approksiu and Detection Engine team: - Fields are barely used; was introduced principally to assist us with dealing with SDHs - Fields are editable via...