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

[Filebeat] CPU consumption spikes, when using filebeat with k8s autodiscovery. #35444

Closed
Evgenikk opened this issue May 12, 2023 · 2 comments
Closed
Labels
needs_team Indicates that the issue/PR needs a Team:* label Stalled

Comments

@Evgenikk
Copy link

Evgenikk commented May 12, 2023

We run filebeat as a daemonset in Kubernetes clusters to send logs to Kafka. Seems like sometimes filebeat restarts all harvesters, which leads to CPU usage spikes. We noticed this problem after this changes.

In our case, we've fixed it by removing this block of code, but it is not the proper solution and can't be used in the upstream.

In this graph, you may see CPU consumption of filebeats before and after our "fix":
image

  • Version: filebeat-oss:8.7.1
  • Operating System: Ubuntu 20.04.5 LTS (GNU/Linux 5.15.0-1033-aws aarch64),
  • Kubernetes version: AWS EKS 1.21
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 12, 2023
@botelastic
Copy link

botelastic bot commented May 12, 2023

This issue doesn't have a Team:<team> label.

@Evgenikk Evgenikk changed the title CPU consumption spikes, when using filebeat with k8s autodiscovery. [Filebeat] CPU consumption spikes, when using filebeat with k8s autodiscovery. May 12, 2023
@botelastic
Copy link

botelastic bot commented Jun 11, 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 Jun 11, 2024
@botelastic botelastic bot closed this as completed Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label Stalled
Projects
None yet
Development

No branches or pull requests

1 participant