-
Problem report
-
Resolution: Duplicate
-
Trivial
-
None
-
None
-
None
-
None
After upgrade Zabbix from version 3.4 to version 4.0, historical problems (generated in version 3.4) has a *UNKNOWN* value in name field instead for example client name.
New alarms (generated in version 4.0) have correct names (for the same trigger).
In file 01_Alarm_list.png there is a list of all alarms (after Zabbix upgrade).
In files 02_Event_details_ for_alarms_generated_after_upgrade.png and 0*3_Event_details_for_alarms_generated_before_upgrade.png* are details for alarm before/after upgrade.
There is the same trigger but for "old" alarms UNKNOWN values appears.
Trigger:
30999 - {{ITEM.VALUE1}.regsub("lastActivityType.*\"(.*)\"", "\1")} for {{ITEM.VALUE1}.regsub("lastActivityClient.*\"(.*)\"", "\1")} {{ITEM.VALUE1}.regsub("lastActivityGroup.*\"(.*)\"", "\1")} failed - client error(s)
zabbix_traps.tmp file attached.
After investigation for version 3.4 there is a table like this:
MariaDB [zabbix]> select * from problem where eventid = 32;
--------------------------------------------------------------------------------------
| eventid | source | object | objectid | clock | ns | r_eventid | r_clock | r_ns | correlationid | userid |
--------------------------------------------------------------------------------------
| 32 | 0 | 0 | 16294 | 1583137205 | 71705220 | NULL | 0 | 0 | NULL | NULL |
--------------------------------------------------------------------------------------
In version 4.0 like this:
MariaDB [zabbix]> select * from problem where eventid = 32;
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| eventid | source | object | objectid | clock | ns | r_eventid | r_clock | r_ns | correlationid | userid | name | acknowledged | severity |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 32 | 0 | 0 | 16294 | 1583137205 | 71705220 | NULL | 0 | 0 | NULL | NULL | 30999 - UNKNOWN for UNKNOWN UNKNOWN failed - client error(s) | 0 | 3 |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
In my opinion during conversion there is a process Event name update and in this moment UNKNOWN values appears in data base.
Steps to reproduce:
Upgrade Zabbix from version 3.4 to 4.0
Expectation:
After upgrade "old" alarms and "new" should appear with correct names.
Please make a procedure how to restore data for "old" alarms.
- duplicates
-
-
- Closed
-