-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Provide a performance tuning guide for Beats #3850
Comments
@ppf2 Thanks for opening this item. I removed the performance tuning item from my list intentionally after meeting with Monica a couple months ago. The item was part of my personal "wish list" for documentation, but it didn't represent what was actually in our plans for the near future. I still think it's a worthwhile effort; I just didn't want to cause confusion (but it seems that I have anyhow). :-) I'll talk to the team about whether we should make this work a higher priority. |
Just noticed that this is a duplicate of #2638. I'll close the other issue and keep this one open. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue doesn't have a |
This issue has been open for a very long time. I'm sorry that we have not been able to provide this content. I'm closing this issue for now, but feel free to open an issue in the observability-docs repo against the Elastic Agent docs if you think we should provide this content for Elastic Agent. |
When we moved the unsolved items from #871 to #2482 and then to #3019, the performance tuning guide didn't get carried over:
Given the various options we expose that can affect performance, it will be helpful to provide a performance tuning guide similar to what we have on the Logstash side so end users will know what settings are recommended (eg. spool_size, output pipelining, workers, publish_async, etc..), what are basic tuning sections vs. advanced, etc..
The text was updated successfully, but these errors were encountered: