[ZBX-12012] In the macro {ITEM.LOG.SEVERITY}, the value "critical" is expanded to "unknown". Created: 2017 Apr 03  Updated: 2017 May 30  Resolved: 2017 May 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.2.18rc1, 3.0.9rc1, 3.2.5rc1, 3.4.0alpha1
Fix Version/s: 2.2.19rc1, 3.0.10rc1, 3.2.7rc1, 3.4.0alpha1

Type: Incident report Priority: Major
Reporter: Kazuo Ito Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: macros
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Team: Team B
Sprint: Sprint 6, Sprint 7
Story Points: 0.25

 Description   

In the macro {ITEM.LOG.SEVERITY], the value "critical" is expanded to "unknown".


The following is the source of the 2.2.17.

const char	*zbx_item_logtype_string(unsigned char logtype)
{
	switch (logtype)
	{
		case ITEM_LOGTYPE_INFORMATION:
			return "Information";
		case ITEM_LOGTYPE_WARNING:
			return "Warning";
		case ITEM_LOGTYPE_ERROR:
			return "Error";
		case ITEM_LOGTYPE_FAILURE_AUDIT:
			return "Failure Audit";
		case ITEM_LOGTYPE_SUCCESS_AUDIT:
			return "Success Audit";
		default:
			return "unknown";
	}
}
#define ITEM_LOGTYPE_INFORMATION	1
#define ITEM_LOGTYPE_WARNING		2
#define ITEM_LOGTYPE_ERROR		4
#define ITEM_LOGTYPE_FAILURE_AUDIT	7
#define ITEM_LOGTYPE_SUCCESS_AUDIT	8
#define ITEM_LOGTYPE_CRITICAL		9
#define ITEM_LOGTYPE_VERBOSE		10

CRITICAL and VERBOSE appear not to be expanded.

The sources of Zabbix 3.0.8 and Zabbix 3.2.4 are also the same.



 Comments   
Comment by Alexander Vladishev [ 2017 May 05 ]

Fixed in:

  • pre-2.2.19 r67857
  • pre-3.0.10 r67858
  • pre-3.2.7 r67859
  • pre-3.4.0 r67860
Generated at Fri Mar 29 13:53:02 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.