[ZBX-9913] Inconsistency in behaviour and error messaging of trigger functions Created: 2015 Sep 28  Updated: 2024 Apr 10  Resolved: 2018 Aug 09

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 4.0.0beta1, 4.0 (plan)

Type: Problem report Priority: Trivial
Reporter: Glebs Ivanovskis (Inactive) Assignee: Arets Paeglis (Inactive)
Resolution: Fixed Votes: 1
Labels: consistency, triggerfunctions, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: DEV-591
Team: Team C
Team: Team C
Sprint: Sprint 38, Sprint 39, Sprint 40
Story Points: 3

 Description   
  • Some of trigger functions (newer ones) have char **error argument and pass error messages back to frontend, some of them don't.
  • Some of trigger functions become not supported in case of any error, some (most recent) try to stay supported and return special error code instead in case of temporary errors.
  • Some trigger functions report a specific error message if they failed to get data from value cache, some of them don't.

It would be good to make error messages, error logging and becoming not supported more consistent across the whole range of supported trigger functions.



 Comments   
Comment by Glebs Ivanovskis (Inactive) [ 2016 Mar 01 ]

Related issue ZBX-10312.

Comment by Arets Paeglis (Inactive) [ 2018 Aug 09 ]

Available in 4.0.0alpha10 (trunk) r83666.

Generated at Fri Apr 19 02:52:29 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.