Call for discussion on ZABBIX 1.6

[nightstrike.lalith]

Some suggestions

I'm not really sure if this isn't there or not, but I think it'd be nice if the user could make define his own macros. It'll add to the flexibility.

[sege]

What happened to escalations in version 1.6? It disappeared in the latest news when releasing 1.5.3.

Will it not be in 1.6? Just repeated alarms? Of will not even that be in there?

[Alexei]

What happened to escalations in version 1.6? It disappeared in the latest news when releasing 1.5.3.

Will it not be in 1.6? Just repeated alarms? Of will not even that be in there?

While this is off-topic, please, read release notes carefully. Support of escalation is already there, in 1.5.3!

[sege]

While this is off-topic, please, read release notes carefully. Support of escalation is already there, in 1.5.3!

I'll go and die for a while. Sorry. I've kept an eye on next.php and haven't seen any changes there so I.. well, sorry again and VERY VERY nice work then!

Edit: please delete my msgs, I'm ashamed.

[vikty]

Sorry,

Whene could they see the 1.6??

In the site It has released for the March 2008...

[Dominic.David]

Traceroute

Hi,

it would be very good, if I can send a Traceroute from the Zabbix Server to the host IP, when the Trigger comes Active.
And send the result of the traceroute with an E-Mail to the Groupmembers for these host.

I have write down a post in the Zabbix-Forum:

http://www.zabbix.com/forum/showthread.php?t=9766

Perhaps it is posible to integrate it in the new Zabbix Version.

MfG
Dominic

[just2blue4u]

The max value for "Refresh unsupported items (in sec)" is "65535".
I set it that high because my zabbix logfile is full of entries caused by items that are not supported and refreshed.

Perhaps it could be possible to let the zabbix server write 2 logs:
One for critical errors like DB problems or unreachable hosts and the other for informational stuff like unsupported items.

Yes, one can simply set DebugLevel to 0 or 1, but that would mean if there is a problem with an item, you must change DebugLevel and restart the server just to get more information about that.

[just2blue4u]

connections in maps: Change labels "OFF" to "UP" and "ON" to "DOWN"

I find the state labels for connections in maps very confusing:
OFF means "The connection is ok", ON means "it isn't".
I guess this is because of the triggers, where true means "something bad is happening". But i don't think it is the correct labeling for connections.

I made my first map a few days ago and assigned the thick, red line to OFF and the thin, green one to ON without doing any research which could mean what.
I was quite sure, ON means "The connection is ON", and OFF means "The connection is OFF". Then i was wondering why all lines kept red though all triggers were false.

I am really sure i'm not the only one who instinctivly assigned the colors and lines wrong. Maybe you can label them more precisely:
Change "OFF" to "UP" and "ON" to "DOWN". That would be less confusing, i think.

[just2blue4u]

Offline Hosts in "latest data"

Yes, i know, the latest data tab is just for checking the latest values of a host.
But we monitor many items for each host and don't need graphs for each.

Sometimes, when a host goes down, we'd like to see its latest values. Unfortunately, that host isn't listed in "latest data", because it's down.

How about the possibility to list hosts that are down but not "disabled" in the dropdown host list in "latest data"?

[just2blue4u]

hi, it's me again...

Just thought about how nice it would be if there was a update-button/link for each trigger listed on the tr_status page, which forces the trigger and all its items to update immediately.

[just2blue4u]

agent hangs on timed out UserParameter (caused by unreachable NFS mount)

Mmh... am i the only one reading this thread?
Hope my suggestions are seen...

Well, today our NFS Server was shut down without unmounting it on all NFS Clients. We have a Zabbix UserParameter "files.open", that contains

#UserParameter=files.open,/usr/sbin/lsof|grep -v lsof|grep -v grep|wc -l|sed s/" "//g

to count all open files on the Client.
This Command hung on the mounted (and unreachable) NFS dir. That caused our agents to hang, too. After killing the lsof procs and restarting the agents, everything was fine again (deactivated the UserParameter line in config).

I'd really like to see Zabbix killing alle UserParameters that time out or at least being more immune/resistent/independent to hanging UserParameters.

(Issue seen on Server 1.4.4, agent 1.4.2)

[swaterhouse]

Mmh... am i the only one reading this thread?
Hope my suggestions are seen...

I would actually qualify this as a bug as much as a feature request. Maybe it would be better submitted to the bug tracker?

[richlv]

first, no, you are not the only one
second, that's a hard nfs mount. that's just how they behave.
you could use softmounts, but things can break badly if you do.
i'm not sure how much would some timeouts help in case of zabbix agent - there are very few, if any, applications that behave really well with stalled nfs mounts. on the positive note, all apps resume nicely when nfs connection is resumed

[just2blue4u]

My "bug" moved here: http://www.zabbix.com/forum/showthread.php?p=35391

[vinhthach]

A few suggestions

1. Template:
-To be able to Clone Applications
- When updating Items Template, Enable/Disable should not overwrite the current setting of host; like the Triggers Template keeps the Enable/Disable setting of host.

2. Screen:
- To be able to create a screen with a Resource similar to "Trigger Overview" but showing ONLY Triggers which go OFF, not the whole long list of Triggers which are OK.
- Another Resource similar to the "System Status" on the main page

3. Graph:
- The display of Trigger does not work well with "Calculated" or "Calculated [Min=0]". Low threshold is not shown with "Calculated [Min=0]"; High threshold is not shown with "Calculated". Only "Fixed" works fine.
- The display of Trigger does not work when the Threshold is an expression.

4. Actions:
- To be able to configure alert message be sent to different Person or Group according to working hour.