Hello, Victor
and thank you for your reply, you're being very helpful as usual.
Regarding "conditions", I'm actually talking about extending an already implemented feature (right click on container, create condition..., Events and Status/Script). The only thing that is missing IMHO is the possibility to apply "unknown" status to child objects... or more like a mix of "unknown" and "unmanaged", as the idea is to stop all DCI polling until the condition is met again.
I'll try to elaborate some more... for some of my coworkers, a container with a big red "critical" status implies that something is wrong with the objects it contains (especially when they all also turn "critical"). It takes ages for them to figure out that the problem is actually due to NetXMS not being able to access its child objects because of a small red "critical" condition on a single, seemingly unrelated node and/or interface.
and thank you for your reply, you're being very helpful as usual.
Regarding "conditions", I'm actually talking about extending an already implemented feature (right click on container, create condition..., Events and Status/Script). The only thing that is missing IMHO is the possibility to apply "unknown" status to child objects... or more like a mix of "unknown" and "unmanaged", as the idea is to stop all DCI polling until the condition is met again.
I'll try to elaborate some more... for some of my coworkers, a container with a big red "critical" status implies that something is wrong with the objects it contains (especially when they all also turn "critical"). It takes ages for them to figure out that the problem is actually due to NetXMS not being able to access its child objects because of a small red "critical" condition on a single, seemingly unrelated node and/or interface.