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

[Stack Monitoring] Document timeout settings #34255

Open
miltonhultgren opened this issue Jan 13, 2023 · 2 comments
Open

[Stack Monitoring] Document timeout settings #34255

miltonhultgren opened this issue Jan 13, 2023 · 2 comments
Labels
Feature:Stack Monitoring Module:beat The beat Metricbeat module Module:elasticsearch Elasticsearch Beats modules Module:kibana Kibana Beats modules Module:logstash Logstash Beats modules Stalled Team:Monitoring Stack Monitoring team

Comments

@miltonhultgren
Copy link
Contributor

Within Metricbeat there is a base timeout of 10 seconds which correlates to the default period setting, this is to avoid calls taking longer than the period to ensure the data is as fresh as the configuration expects.

There are cases where we need to extend the period, such as when an endpoint takes longer to reply for "good" reasons. One example of this is the _cluster/stats endpoint of Elasticsearch for a large cluster state. But, simply setting the period to 20 seconds (for example) isn't enough, since we'll hit the request timeout limit instead.

The below settings can be used to raise the timeout:

- module: elasticsearch
  xpack.enabled: true
  period: 30s
  connect_timeout: 30s
  timeout: 30s

These settings are not well documented (and when to use them is also not documented).

AC

  • The different timeout settings and when they might be needed is documented in the documentation for the modules we own
  • The internal Knowledgebase entry for support is updated to reference the newly added documenttion
@miltonhultgren miltonhultgren added Team:Infra Monitoring UI - DEPRECATED Infrastructure Monitoring UI team - DEPRECATED - Use Team:Monitoring Module:beat The beat Metricbeat module Module:logstash Logstash Beats modules Module:kibana Kibana Beats modules Module:elasticsearch Elasticsearch Beats modules labels Jan 13, 2023
@botelastic
Copy link

botelastic bot commented Jan 24, 2024

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jan 24, 2024
@smith smith added the Team:Monitoring Stack Monitoring team label Jan 26, 2024
@botelastic botelastic bot removed the Stalled label Jan 26, 2024
@smith smith removed the Team:Infra Monitoring UI - DEPRECATED Infrastructure Monitoring UI team - DEPRECATED - Use Team:Monitoring label Jan 26, 2024
@botelastic
Copy link

botelastic bot commented Jan 25, 2025

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Stack Monitoring Module:beat The beat Metricbeat module Module:elasticsearch Elasticsearch Beats modules Module:kibana Kibana Beats modules Module:logstash Logstash Beats modules Stalled Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

3 participants