Ad Widget

Collapse

trigger on vm.memory.size[pused] does not work

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • BlackCrystal
    Junior Member
    • Dec 2018
    • 28

    #1

    trigger on vm.memory.size[pused] does not work

    hi
    i defined an item named 'Used Memory in perc' in my OS template with 'vm.memory.size[pused]' as its key. i defined below trigger on it:


    (({Template OS:vm.memory.size[pused].last()}>70) and ({Template OS:vm.memory.size[pused].time()}<000000 or {Template OS:vm.memory.size[pused].time()}>0630000)) or (({Template OS:vm.memory.size[pused].last()}>90) and ({Template OS:vm.memory.size[pused].time()}>000000 or {Template OS:vm.memory.size[pused].time()}<063000))

    it mean if used memory went beyond 70 percent between 06:30 and 23:59 and beyond 90 percent between 00:00 and 06:29 then send an alert. i noticed that one of my hosts has 80% memory usage but trigger didn't activated. trigger is enabled and i see no errors anywhere. what should i do?
  • BlackCrystal
    Junior Member
    • Dec 2018
    • 28

    #2
    i found the solution. actually the > and < are not correct. the right expression is:
    (({Template DB2 OS:vm.memory.size[pused].last()}>70) and ({Template DB2 OS:vm.memory.size[pused].time()}>0630000 or {Template DB2 OS:vm.memory.size[pused].time()}<235900)) or (({Template DB2 OS:vm.memory.size[pused].last()}=100) and ({Template DB2 OS:vm.memory.size[pused].time()}>235900 or {Template DB2 OS:vm.memory.size[pused].time()}<063000))

    Comment

    Working...