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

[Ingest Manager] Send long polling timeout to the agent #77106

Closed
nchaulet opened this issue Sep 9, 2020 · 3 comments
Closed

[Ingest Manager] Send long polling timeout to the agent #77106

nchaulet opened this issue Sep 9, 2020 · 3 comments
Labels
enhancement New value added to drive a business result Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@nchaulet
Copy link
Member

nchaulet commented Sep 9, 2020

Description

Related to elastic/beats#21037

We should send the long polling timeout to the agent so it can be use it to set a proper timeout.

It should be in the config change action probably something like

id: 75c06f20-f2a6-11ea-be6c-157b32ff6ced
revision: 1
outputs:
  default:
    type: elasticsearch
    hosts:
      - 'http://localhost:9200'
agent:
  monitoring:
    enabled: true
    use_output: default
    logs: true
    metrics: true
+  checkin_timeout: 60000
@nchaulet nchaulet added the Team:Fleet Team label for Observability Data Collection Fleet team label Sep 9, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@blakerouse
Copy link

Being that we are also going to add the URL's to contact Fleet in the configuration, maybe we should include it in the same kibana block?

@ph ph added the enhancement New value added to drive a business result label Oct 19, 2020
@jen-huang
Copy link
Contributor

We use Fleet Server now. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

5 participants