NetXMS Forum

It's not possible now. I see that this is a common requirement (along with possibility to create calculated DCIs), so I definitely will implement this in one of the future versions. Best regards, Victor

Unfortunately not. However, I can add it in 0.2.19 - there are no much work, just nobody asking about such feature before. Best regards, Victor

Hello! "Calculate status as" determines how object's status should be calculated based on child objects statuses. For objects without child objects (like conditions) it has no meaning. "Propagate status as" determines how object present it's status to parent object(s). For example, you have a switch with various interfaces. Normally, when interface goes down, it's status changes to CRITICAL, and status of entire node object changes to CRITICAL (and so on up to the root). However, if you have not very important interfaces and wish that node status changes not to CRITICAL, but to WARNING when this interface  goes down, you can change "Propagate status as" property of interface object so it will propagate it's CRITICAL status as WARNING. Best regards, Victor

Yes, you can use extended form of PDH.CounterValue: PDH.CounterValue("counter name",1) If second argument is present in PDH.CounterValue and set to non-zero, then agent will get two samples with 1 second interval, and use them to calculate resulting value.