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

Ability to turn compression/gzip on for callCluster in alert and action executors #50212

Closed
mikecote opened this issue Nov 11, 2019 · 5 comments
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

No description provided.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@ymao1
Copy link
Contributor

ymao1 commented Mar 4, 2021

@FrankHassanabad Is this still something that SIEM needs from alerting?

@ymao1
Copy link
Contributor

ymao1 commented Mar 4, 2021

@elastic/kibana-core Is this something that should be handled automagically by core or do we need to do something in particular to enable this?

@mshustov
Copy link
Contributor

mshustov commented Mar 5, 2021

@ymao1 Could you elaborate on what exactly, please? The issue doesn't provide any description. Do you want to be able to compress the request body when sending a request to the Elasticsearch service? If so, the new Elasticsearch client supports gzip compression out-of-the-box.
See compression in the official doc https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/basic-config.html

@mikecote
Copy link
Contributor Author

mikecote commented Mar 5, 2021

@restrry more details from SIEM can be found here #50222 under "Control compression and timeout".

Based on that, the new Elasticsearch client that we provide to them supports this now and this issue and #50217 are probably no longer necessary.

@ymao1 ymao1 closed this as completed Mar 18, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

6 participants