-
Problem report
-
Resolution: Unresolved
-
Trivial
-
None
-
7.2.1
Now in Redis by Zabbix agent 2 template redis configuration parameter `mem_fragmentation_ratio` is used.
According to https://github.com/redis/redis/issues/9256#issuecomment-883577803 `allocator_frag_ratio` instead of `mem_fragmentation_ratio` .
Example:
- - macro: '\{$REDIS.MEM.ALLOCATOR_FRAG_RATIO.MAX.WARN}'
- value: '1.5'
- description: 'Maximum memory allocator fragmentation ratio (real frag ratio)'
* name: 'Allocator fragmentation ratio'
- type: DEPENDENT
- key: redis.memory.allocator_fragmentation_ratio
- value_type: FLOAT
- description: 'Ratio between allocator_active and allocator_allocated. This is the true (external) fragmentation metric (not mem_fragmentation_ratio).'
- preprocessing:
- - type: JSONPATH
- parameters:
- - $.allocator_frag_ratio
- master_item:
- key: redis.memory.info_raw
- tags:
- - tag: component
- value: memory
- triggers:
- expression: 'min(/Redis by Zabbix agent 2/redis.memory.allocator_fragmentation_ratio,15m)>\{$REDIS.MEM.ALLOCATOR_FRAG_RATIO.MAX.WARN}'
- name: 'Memory allocator fragmentation ratio is too high'
- event_name: 'Memory fragmentation ratio is too high (over \{$REDIS.MEM.ALLOCATOR_FRAG_RATIO.MAX.WARN} in 15m)'
- priority: WARNING
- description: 'Ratio between allocator_active and allocator_allocated. This is the true (external) fragmentation metric (not mem_fragmentation_ratio).'
- tags:
- - tag: scope
- value: performance