Hi all.
I'm using ZenOSS to monitor our proxmox servers.
During the modelling phase, ZenOSS will grab an initial processlist and match against a table of known processes that should be running.
Trouble is, it's picking up the processes running inside the various containers.
When a process stops in a container that happens to be unique (ie the process is only running in that container), we get two alerts. One for the container and one for the proxmox host.
I've seen that you can hide processes running inside containers from the host node by setting
.
However, I read on the OpenVZ wiki (https://openvz.org/Processes_scope_and_visibility) that this will break live migration and checkpointing.
Has anyone else dealt with this kind of issue?
Thanks
I'm using ZenOSS to monitor our proxmox servers.
During the modelling phase, ZenOSS will grab an initial processlist and match against a table of known processes that should be running.
Trouble is, it's picking up the processes running inside the various containers.
When a process stops in a container that happens to be unique (ie the process is only running in that container), we get two alerts. One for the container and one for the proxmox host.
I've seen that you can hide processes running inside containers from the host node by setting
Code:
[COLOR=#000000][FONT=Liberation Mono]kernel.pid_ns_hide_child=1[/FONT][/COLOR]However, I read on the OpenVZ wiki (https://openvz.org/Processes_scope_and_visibility) that this will break live migration and checkpointing.
Has anyone else dealt with this kind of issue?
Thanks