Hello, I use this expression, i'ts working perfect:
({TRIGGER.VALUE}=0 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<250000000) | ({TRIGGER.VALUE}=1 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<(250000000+100000000))
I wish to use in megabytes or terabytes, but I see an error when change trigger:
({TRIGGER.VALUE}=0 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<250M) | ({TRIGGER.VALUE}=1 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<(250M+100M))
In each host, status of the trigger changes from active to unkown.
Any suggestion? I use this for memory and storage (terabytes), too many zeroes expressing in bytes
({TRIGGER.VALUE}=0 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<250000000) | ({TRIGGER.VALUE}=1 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<(250000000+100000000))
I wish to use in megabytes or terabytes, but I see an error when change trigger:
({TRIGGER.VALUE}=0 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<250M) | ({TRIGGER.VALUE}=1 & {LUCE-Server Linux:vm.memory.size[available].last(1m)}<(250M+100M))
In each host, status of the trigger changes from active to unkown.
Any suggestion? I use this for memory and storage (terabytes), too many zeroes expressing in bytes