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
in_mem: add MemAvailable, Buffers and Cached from /proc/meminfo #3092
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Filipe Pina <fopina@gmail.com>
7ee63b2
to
8c0e5fe
Compare
debug log for
Valgrind log attached |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
@edsiper anything missing to make this of interest or should I let it close? |
busybox is GPLv2. I think they are not compatible.
|
thanks @nokute78 that makes sense. I'm bit off opensource licenses and common practices though in this case it's like 20 lines in bbfree.h. |
It is licensed under GPLv2 even if only 20lines. If we merge such code, the license of Fluent-bit will become GPLv2. FYI |
ok, I’ll rewrite it. Apart from licensing, does the PR look good to you (and does it make sense)? |
Thank you. I remember similar pull request #1617
If no option, when user update fluent-bit, new values are appended. Ubuntu 14.04 is supported until 2022 and its kernel version is v3.13. ref |
I must have missed that PR but I guess this is still useful as the author gave up on it. I’ll rephrase the commit message. |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
@nokute78 thoughts on this ? |
I completely forgot about the PR as I’ve been using it as separate module. |
just rebase on top of GIT Master, for Ubuntu >= 16.04 or centos >= 7 should be fine |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
8c0e5fe
to
24de32f
Compare
24de32f
to
8de980b
Compare
Signed-off-by: Filipe Pina <fopina@gmail.com>
8de980b
to
514ebb7
Compare
@edsiper ✅ rebased and moved the code around a little bit, looking forward to have this merged and dropping my external plugin :) |
@niedbalski was there activity as it is meant to be merged? |
@niedbalski worth pushing conflict resolution? I already did in the standalone copy of the module |
in_mem plugin modified to include MemAvailable (from /proc/meminfo)
the
sysinfo
syscall exposessi_meminfo
from the kernel butMemAvailable
is calculated bysi_mem_available
and not exposed in any syscall, only in/proc/meminfo
(kernel meminfo srcThe
free
command, part of procps, parses/proc/meminfo
- free calls meminfo function that parses itTo avoid adding libprocps as dependency, I chose to copy&paste busybox implementation - also parses
/proc/meminfo
but the piece of code that does the parsing is small and easy to port.Note I am currently using this as standalone plugin without any issues, so tested and available in case anyone wants to use it (before merge)
Enter
[N/A]
in the box, if an item is not applicable to your change.Testing
Before we can approve your change; please submit the following in a comment:
Documentation
fluent/fluent-bit-docs#467
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.