PID/HostPID and PPID/HostPPID values getting printed in e-notation about kubearmor-client HOT 8 OPEN

@Ankurk99, this happens when the process ID gets a value greater than a million. I am still trying to solve the problem that is causing this output.

@sahilsarawagi , it is completely normal to get a PID/PPID value greater than a million. The default pid_max value in Linux kernel is 2^22.

The ask here is to print the pid/ppid in a regular non-enotation format.

from kubearmor-client.

Valid for PID and PPID as well, when you keep the containers running long enough...

from kubearmor-client.

Thanks a lot @sahilsarawagi for your interest to work on this, feel free to ask anything related to this issue in this thread or on our slack channel ✌🏽

from kubearmor-client.

Hey @sahilsarawagi! Is there any update on this issue? Do you need any help?

from kubearmor-client.

please assign me this issue, I want to work on this.

from kubearmor-client.

@Ankurk99, this happens when the process ID gets a value greater than a million. I am still trying to solve the problem that is causing this output.

from kubearmor-client.

@nyrahul, I was saying that the $ karmor log starts giving the PID value in enotation form, when the value of PID exceeds greater than a million. I am still trying to find out which coding error which is causing this enotation format. As I am new to this enviroment that's why it taking so long.

from kubearmor-client.

@sahilsarawagi no worries, take your time. A hint here might be this started happening when we changed to a generic printing format for all the fields in the telemetry event,

from kubearmor-client.