BUG :: 1.1-beta7 trigger function logseverity

[SAT QPass]

There appears to be a bug either in the storage mechanism or the table itself for the trigger function "logseverity".

The only way the GUI will let you create it is if you call it "logseverity(0)", however, it is stored in the database as "logseverit" and is subsequently displayed as "logseverit" via the GUI.

----         23 |  10429 |         2 | NULL      | logseverit | 0

Obviously, should you attempt to modify the trigger and then click save you are immediate confronted with the error that logseverit is not a know function.

Thanks,

Aaron

[swaterhouse]

I can confirm that this still happens in Beta8. If I could get this to work I would switch all my windows hosts over to Zabbix.

Scott

[753713]

Hi,

i have the same Error in Zabbix beta9, logseverity replace with logseverit

Ideas???

Chris

[Alexei]

To be fixed in 1.1beta10. A fix is already posted somehere else.