-
Notifications
You must be signed in to change notification settings - Fork 23
Add alert when fluentd queue buffers grow too large #1048
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
Conversation
Should we not warn at 100MiB as that is what the default Opensearch |
I am open to suggestions, I just picked a random number. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Pierre.
I think Dawud has a point that until we fix https://stackhpc.atlassian.net/browse/INFRA-666, a lower threshold would be useful, but we should make https://stackhpc.atlassian.net/browse/INFRA-666 a priority.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something is better than nothing. Since the INFRA-666 task is still on the backlog, I propose we move forward with this and we can update it with something more fancy down the line.
Though, we should probably rebase this change onto antelope
100 MiB seems like a sane default (99MiB could still technically be posted) |
No description provided.