[ZBXNEXT-2445] increase trigger error size limit from 128 to 2048 Created: 2014 Sep 07  Updated: 2024 Apr 10  Resolved: 2017 Mar 30

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Installation (I)
Affects Version/s: 2.4.0
Fix Version/s: 3.4.0alpha1

Type: Change Request Priority: Minor
Reporter: richlv Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: error, triggers, trim
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBX-11583 The end of sentence is not visible in... Closed
is duplicated by ZBX-11879 Incomplete message from server Closed
Team: Team A
Sprint: Sprint 4
Story Points: 1.5

 Description   

ZBXNEXT-2203 increase item error field from 128 to 2048. unfortunately, longer error messages also end up in trigger error field which is still limited to 128 chars. it would be beneficial to increase trigger error field limit - probably to 2048, too

 Comments   
Comment by Oleksii Zagorskyi [ 2016 May 17 ]

An example of truncated and complete error messages:

Cannot evaluate function "Zabbix server:agent.ping.nodata(5m)": item does not have enough data after server start or item creati
Cannot evaluate function "Zabbix server:agent.ping.nodata(5m)": item does not have enough data after server start or item creation.

such truncation becomes more noticeable if use for example new macros suggested in ZBXNEXT-3140

Comment by Andris Mednis [ 2017 Mar 09 ]

'hosts' table columns 'error', 'ipmi_error', 'snmp_error, and 'jmx_error' are up to 2048 chars.
'items' table column 'error' is 2048, too.
'triggers' table 'error' and 'alerts' table 'error' are limited to varchar(128). Let's go 2048 !

Comment by Andrea Biscuola (Inactive) [ 2017 Mar 21 ]

Fixed in svn://svn.zabbix.com/branches/dev/ZBXNEXT-2445

Increased the size for triggers.error and alerts.error to 2048 characters. Modified also the database version and added the related
C function to the upgrade procedure. Modified the front-end files with the new fields sizes and the new database version.
Maybe some checks are needed by the front-end developers.
Tested both the bootstrap of a new DB and the upgrade from an existing one.

Comment by Andrea Biscuola (Inactive) [ 2017 Mar 24 ]

(1) Forgot to fix the database version in the creation script.
RESOLVED in r66699

s.paskevics CLOSED.

Comment by Sergejs Paskevics [ 2017 Mar 24 ]

(2) Please correct the defined errors size from the server side and check my minor changes in r66704.
db.h:

#define ALERT_ERROR_LEN			128

#define TRIGGER_ERROR_LEN		128

abs RESOLVED in 66705.

abs All good also with the changes in r66704

s.paskevics Sorry, I didn't notice that we do not use TRIGGER_ERROR_LEN, please remove it. REOPENED.

abs RESOLVED in r66795

s.paskevics CLOSED.

Comment by Sergejs Paskevics [ 2017 Mar 27 ]

Successfully tested.

Comment by Andrea Biscuola (Inactive) [ 2017 Mar 28 ]

Fixed in

  • 3.4.0alpha1 (trunk)
Comment by Martins Valkovskis [ 2017 Mar 29 ]

Documented in what's new for 3.4.

sasha Under this development also has been increased size of error field for alerts.

REOPENED

martins-v RESOLVED

sasha Thanks! CLOSED

Generated at Tue Jun 03 18:26:49 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.