Hello Patrik,

In terms of memory utilisation pused will show data differently:

$ zabbix_agentd -t vm.memory.size[pavailable]
vm.memory.size[pavailable]                    [d|48.995366]

$ zabbix_agentd -t vm.memory.size[pused]
vm.memory.size[pused]                         [d|88.454704]

https://www.kernel.org/doc/Documentation/filesystems/proc.txt
https://www.zabbix.com/documentation/current/manual/appendix/items/vm.memory.size_params

Also please note, description of the item is provided correctly:

Memory used percentage is calculated as (100-pavailable)

Regards,
Edgar

ok i see your point

avaialable is showing more then free also buffers etc. so indeed pused is not an option.

still the trigger is confusing due to the javascript as one would think available memory is ex 36% but with the JS now we have 63% as value so for the macro in our trigger we have to use a macro of 90% for pavailable instead of 10% 

this makes the trigger very confusing

Problem:

>{$MEMORY.UTIL.MAX}

Hello Patrik,

Template description: Memory used percentage is calculated as (100-pavailable)

• Item name: Memory utilization
• Item key: vm.memory.size[pavailable]
• Item preprocessing: 100-vm.memory.size[pavailable]
• Trigger name: High memory utilization ( >{$MEMORY.UTIL.MAX}% for 5m)
• Trigger configuration: {Zabbix server:vm.memory.size[pavailable].min(5m)}>{$MEMORY.UTIL.MAX}

Simplified: Memory utilization > macro {$MEMORY.UTIL.MAX} = report problem, if changes required - set this value lower or higher.

There is no separate key for measuring memory utilization. If use your example, the data element and trigger settings will operate with different values, which will lead to confusion: item name - utilization, key and value - memory available, trigger - memory available < X. Using different item name and trigger also confusing.

Currently where is no indication for items if preprocessing is used, you need to open preprocessing tab, covered by: ZBXNEXT-4803, but template is documented and logic for the item looks clear, if not rely only on item key, especially with rich abilities to transform data using preprocessing steps and other options.

Please suggest.

Regards,
Edgar

my point was that JS is not needed here and making the trigger more confusing

i don't know if others agree or not 

documentation is ok that was never my issue 

i really don't see the point of using JS in this item and then building a trigger on this item that works all the way different as one would expect without looking at the preprocessing tabs in the item.

Available in :

• 5.2.0alpha1 (master) 4e6557e1e4b
• 5.0.2rc1 4ff54482f4a