Metricbeat for Kibana collects usage stats once a day.
But, if the collection request fails (we've seen timeouts lately for requests taking longer than 10s default timeout), it will request the usage again on the next poll interval (10s later), overloading the server even more.
|
content, err = m.statsHTTP.FetchContent() |
|
if err != nil { |
|
return err |
|
} |
|
|
|
if shouldCollectUsage { |
|
m.usageLastCollectedOn = now |
|
} |
Can we set up a backoff mechanism that will try to skip the collection of the usage for a few rounds (maybe for another day?), prioritising metric-stats over usage-collection?
Metricbeat for Kibana collects usage stats once a day.
But, if the collection request fails (we've seen timeouts lately for requests taking longer than 10s default timeout), it will request the usage again on the next poll interval (10s later), overloading the server even more.
beats/metricbeat/module/kibana/stats/stats.go
Lines 166 to 173 in 03748b3
Can we set up a backoff mechanism that will try to skip the collection of the usage for a few rounds (maybe for another day?), prioritising metric-stats over usage-collection?