[ZBX-23057] Redis plugin template trigger: Memory fragmentation ratio is too high Created: 2023 Jul 04 Updated: 2024 Feb 22 |
|
| Status: | Confirmed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Agent2 plugin (G) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Martin Lipocky | Assignee: | Zabbix Development Team |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The trigger "Redis: Memory fragmentation ratio is too high" is bound to item redis.memory.fragmentation_ratio. After restarting the redis server the memory fragmentation is always above 10 and the default threshold is 1.5 I found out that the item is reading the INFO value from mem_fragmentation_ratio. |
| Comments |
| Comment by James Howe [ 2024 Feb 22 ] |
|
Redis developers explaining the correct key to be looking at. The template does discover the correct item, but you cannot edit the trigger to use a discovered key. |