image-2022-09-05-13-18-57-342.png
|
Sub-task |
[ZBXNEXT-7960] Increase the length of trigger title Created: 2022 Sep 05 Updated: 2023 Oct 04 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Server (S) |
| Affects Version/s: | 6.0.8 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Minor |
| Reporter: | Aigars Kadikis | Assignee: | Valdis Murzins |
| Resolution: | Unresolved | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
image-2022-09-05-13-18-57-342.png
|
||||
| Issue Links: |
|
||||
| Description |
|
After the LLD rules executes in, if the trigger title reaches over 256 characters, then LLD cannot create it and says:
Cannot update trigger: value "" too long
Real life example: Cannot update trigger: value "/var/lib/lxc/core-abcdefg: Disk space is critically low (used > {$VFS.FS.PUSED.MAX.CRIT.LINUX:"/var/lib/lxc/core-abcdefg"}% and free < {$VFS.FS.FREE.MIN.CRIT.LINUX:"/var/lib/lxc/core-abcdefg"}, for more than {$VFS.FS.TIME.LINUX:"/var/lib/lxc/core-abcdefg"})" is too long. If try to create the trigger manually (without LLD) then frontend automatically truncates the trigger title to 256 characters:
According to documentation, the trigger.description column can hold up to 2048 characters. So it looks like the database is not creating limitation, but process 'zabbix-server' or frontend. |
| Comments |
| Comment by Jeff [ 2023 Oct 04 ] |
|
Arguably this isnt a CR, but in fact a bug. Zabbix kubernetes monitoring is impacted by this problem due to long PVC mount names in trigger generation. Please fix this issue. |
