Hi,
I'm using Zabbix since 1.1Beta8, working great. The latest stable 1.1.4 works also great, but i missed some features in the frontend (user permissions), so I upgraded to latest beta 1.3.1.
The frontend works - but also with some problems:
i tried to restrict groups, not to access some systems by creating a new group, assigning the "deny"-permissions and the stuff the user into this group.
but after that, even my "super admin" cannot access these systems any more - neither in the "monitoring"-section, nor in the "configuration"-tabs.
After revoking the deny-rights from the group, it works again as normal.
the super admin is NOT part of this group!
the next thing:
I monitor webhosting-servers with zabbix, so there is the element: "IMAP-Server is running on {HOSTNAME}". this is being displayed as it should on the monitoring-overview.
then I defined a trigger with "IMAP-Server is down on {HOSTNAME}". The value is also reported as "0", as it should and as i'm used from 1.1.4.
In the notification-mails, i used this as subject:
well - in 1.1.4 this was displayed:
now, with 1.3.1 I get:
after searching the sources, I found the difference between 1.1.4 and 1.3.1:
in file src/zabbix_server/expressions.c, the stable checks against "trigger->triggervalue", but the beta against "event->triggervalue" ... the event is "OFF", so this works ... but the trigger is now "ON", so that's not the text, i want to see ... either use "IMAP-Server is running: OFF" or "IMAP-Server is down: ON" ...
diff-output between expressions.c in 1.1.4 and 1.3.1:
Should i now change the trigger-texts? but then they don't match to the values in the frontend any more ... "IMAP-Server is running: 0", even when all works normal ...
in addition, i wanted to get the reported value from the trigger - e.g. the icmppingsec-value ...
This should get me something like that:
in the stable, this works great ... but beta reports:
if I should provide more details, let me know ...
and sorry for mistakes in the english language, i'm from Germany
Anton
I'm using Zabbix since 1.1Beta8, working great. The latest stable 1.1.4 works also great, but i missed some features in the frontend (user permissions), so I upgraded to latest beta 1.3.1.
The frontend works - but also with some problems:
i tried to restrict groups, not to access some systems by creating a new group, assigning the "deny"-permissions and the stuff the user into this group.
but after that, even my "super admin" cannot access these systems any more - neither in the "monitoring"-section, nor in the "configuration"-tabs.
After revoking the deny-rights from the group, it works again as normal.
the super admin is NOT part of this group!
the next thing:
I monitor webhosting-servers with zabbix, so there is the element: "IMAP-Server is running on {HOSTNAME}". this is being displayed as it should on the monitoring-overview.
then I defined a trigger with "IMAP-Server is down on {HOSTNAME}". The value is also reported as "0", as it should and as i'm used from 1.1.4.
In the notification-mails, i used this as subject:
Code:
{TRIGGER.NAME}: {TRIGGER.VALUE}
Code:
IMAP-Server is down on Venus: ON
Code:
IMAP-Server is down on Venus: OFF
in file src/zabbix_server/expressions.c, the stable checks against "trigger->triggervalue", but the beta against "event->triggervalue" ... the event is "OFF", so this works ... but the trigger is now "ON", so that's not the text, i want to see ... either use "IMAP-Server is running: OFF" or "IMAP-Server is down: ON" ...
diff-output between expressions.c in 1.1.4 and 1.3.1:
Code:
721,722c731,732 < if(trigger->value == TRIGGER_VALUE_TRUE) < snprintf(replace_to, sizeof(replace_to), "OFF"); --- > if(event->value == TRIGGER_VALUE_TRUE) > zbx_snprintf(replace_to, sizeof(replace_to), "OFF");
in addition, i wanted to get the reported value from the trigger - e.g. the icmppingsec-value ...
Code:
{TRIGGER.NAME}: {{HOSTNAME}:{TRIGGER.KEY}}
Code:
Pingtime to Venus is critical: 587ms
Code:
Pingtime to Venus is critical: {Venus:icmppingsec}
if I should provide more details, let me know ...
and sorry for mistakes in the english language, i'm from Germany

Anton
I think all issues you reported were fixed in latest releases of 1.3.x.
Comment