We are having Zabbix server on Centos 5.5 and zabbix proxy on Centos 5.5. Also we are having lots of centos servers and Windows servers which are configured as zabbix agent. We are having their clusters too. We are having all servers on xen servers as VM.

let's consider this one as handling lack of documentation for it services

Expanded documentation section on IT services

i don't think there is point in implementing "integrity check" :

1. it can fail because of an export/import bug. if so, those should be reported separately and fixed;
2. it can fail because latest version has some restrictions that the older version did not have (like allowed symbols in item keys). but in that case older version has no idea about additional restrictions in the latest version.

i'm willing to be convinced of the feasibility of such a feature, but so far i don't see technical way to implement that
different case is xml validation upon import, but that's xml syntax + schema, and that's for import, not export.

1.8.3

OS: CentOS5.3; Zabbix version: 1.8.2

please use forum for support questions, thanks

Project

please zabbix forums for discussion
http://www.zabbix.com/forum/forumdisplay.php?f=4

ZBXNEXT-436

1. map label backgrounds have been regressed in this branch (see the screenshot);
2. including a map in a screen renders an undefined variable warning (see the screenshot)

3. looks like this branch was created at an unfortunate moment - valuemap stuff was split out in a separate file (which was never ever mentioned in a commit message ), and it now fails on many pages :
Failed opening required 'include/valuemap.inc.php'

fixed

if acknowledges are disabled, "Problem display" dropdown should have a tooltip saying "Event acknowledging disabled" or similar

fixed

seems to works as expected in dev branch rev 13253.
for trunk, data.sql should be changed & db patch created

branches/1.8 13261

doesn't dashboard currently display colours based on severity ? changing that to hardcoded colours might limit the amount of information divulged

ZBXNEXT-426

dev branch rev 13135.

dashboard with "separated" enabled, host status widget :
Undefined index: lastUnack[/local/apache2/htdocs/dev/ZBXNEXT-426/include/blocks.inc.php:629]

fixed

hmm. dev branch rev 13139.

setting to "unacknowledged" :
Undefined index: lastUnack[/usr/local/apache2/htdocs/dev/ZBXNEXT-426/include/blocks.inc.php:727]

also, it would probably be easier to understand if "unacknowledged" was renamed to "unacknowledged only"

oh, one more - when set to "unacknowledged [only]" , numbers are not bold red - they should be so that user can quickly identify that this option is enabled

fixed

confirming the implementation in dev branch rev 13145

branches/1.8 13150
overview is not changed

ZBXNEXT-425

!! only for map labels !!

1. these should be documented in http://www.zabbix.com/documentation/1.8/manual/config/macros

2. maybe an issue with missing documentation, but it looks like at least two of them do not operate correctly :

seems to return count of acknowledged events

seems to return 0 even when there are acknowledged triggers in problem state.

fixed

macros in frontend considered working as expected in rev 13106.
for notifications serverside two new macros should be implemented :

confirming the server implementation in dev branch rev 13163

yes

branches/1.8 13187

item (1) means that last option from the first dropdown moves into this new selection.

ZBXNEXT-424

"days" should be all lowercase.
other than that looks fine in dev branch rev 13039.

branches/1.8 13041

WEB Frontend

The mentioned translation file.

translation has escaped doublequotes - \"Multibyte String\"

that should not be necessary - has this translation been created with a recent version of the frontend ?

Translations where exported with Zabbix Frontend from release 12771.

ok, then i'll consider that to be a leftover from some older version - thanks, committed

Available in pre-1.8.3 in r12612.

as discussed, the difference in how frontend and server calculates queue can be very confusing.
in my case frontend shows 16 queued items, but server returns 0 - all 16 have been assigned to hosts that are monitored by a proxy.

there are other differences. to avoid future bugreports, frontend & server calculations should be unified by changing whichever component is less correct in that regard.

Corrections and improvements available in pre-1.8.3 in r12724.

instead, it should modify the fields (probably using js), but not reload items themselves. changing multiple filter values is quite a performance issues with large setups, as it reloads after every dropdown change.

Bug fixed in version pre 1.8.3 revision 12386

Available at version pre1.8.3, rev. 12802.

minor nitpick - proxy port defaults to 10050, but it should default to 10051

Fixed in r12836.

another minor thing. create a passive proxy and point it to some zabbix server. target zabbix server writes really uninformative messages in the logfile :

Incorrect data. Can't find pair with name "host"
Error sending result back

if possible, would be nice to make these somewhat more helpful (if i didn't know what caused them, i'd have no idea what's that)

reopening so that the log entry issue is not lost

Fixed in version pre1.8.3, rev. 12958

log messages filed as ZBX-3823

Web Interface

hmm. this file seems to be corrupt - all strings are empty in there

sorry.... previous one was corrupted... already deleted and added new one... this is updated up to revision 12344 (1.8.x-dev & 1.9.x-dev)

thanks, committed

this should be available in 1.8.3 as the global alarm functionality

1.8.3 11622, 11813

i believe this is not relevant anymore with export functionality being moved into template/host sections

I would like to see this feature as well.

Any chance this could be pushed up the ladder, guys? I just disassociated 21 hosts from their old template so i could link them to an improved template and now every host has all of it's previously templated items linked directly to the host. This is a really huge PITA and a waste of time to have to now go and delete Items (taking Triggers and Graphs with them, thank fully) and Applications from every host.

ZBXNEXT-343

implementation works as expected in dev branch rev 12917.

branches/1.8 12918

slackware linux

This feature request can be closed now because https://support.zabbix.com/browse/ZBX-2011 improved.

Thanks!

14538:20100429:163933.426 Slow query: 262.591837 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14531:20100429:163942.081 Slow query: 106.971386 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14529:20100429:163954.606 Slow query: 180.310498 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14540:20100429:164010.791 Slow query: 126.616977 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14539:20100429:164026.615 Slow query: 133.093000 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14537:20100429:164044.422 Slow query: 102.160601 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14532:20100429:164109.743 Slow query: 180.720213 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14487:20100429:164147.708 Slow query: 151.830678 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14487:20100429:164147.712 Sending list of active checks to [::ffff:192.168.3.2] failed: host [localhost] not found
14534:20100429:164147.713 Slow query: 177.742693 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14536:20100429:164234.889 Slow query: 316.659795 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"
14483:20100429:164335.317 Slow query: 135.042823 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='
eventid'"

Available in version pre1.8.3, r11965.

Hi,

As GDE mentioned on Zabbix forum, this bug is still here in version 1.8.6.

During a stress test we obtained lot of slow query and for large amount of services : server crash

27106:20110926:120928.425 Slow query: 120.509592 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"
27101:20110926:120928.498 Slow query: 66.452517 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"
27107:20110926:120931.416 Slow query: 62.458832 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"
27123:20110926:120934.875 Slow query: 108.504381 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'"

GDE quote :

our database is a postgresql 9.0.4 hosted on a seperate machine from zabbix server.

strangely, this doesn't happen when we test the first 100 hosts.

These results have an impact on zabbix. From the frontend, we see a queue for items that are supposed to be checked by zabbix_agent (or internal) that gets ever increasing until the script stop.
We've also noticed that once the queries are done (which happens a couple minutes after the end of the test, obviously) all graphs get updated.

Thank's in advance

I think it should be implemented for URLs having http:// or https:// prefix only.

seems to work as expected in dev branch rev 12154.

branches/1.8 12163

It will be implemented by introducing a new structure, which will keep list of items currently processed by DB Syncers.

If an itemid is buing processed, other DBSyncer won't pick it up from the history buffer.

Added new configuration parameter StartDBSyncers.
Available from v. pre1.8.3, r11801

How will we know if this is working?

Reason I ask, is that I have Zabbix monitoring with a small setup:
Hosts: 127/20/64
Items: 4615/117/31
Triggers: 1934/17
Required NVPS 132.67

And the issue is that 27 of these hosts I am actively logging log data (e.g. error.log, access.log, etc.), roughly 2 logs each host, at 10 lines per second. So the theoretical maximum is 540 lines/sec of log(text) data. Also I have a trigger assigned to all the logs - nothing special, just a simple REGEX on each, and performing an alert if it is matched.

Now when I do a mysql processlist, I almost always see just 1 thread running, even if DBSyncers is 4, 16, 32. The DBSyncers value to be honest is irrelevant.

Now when I increased my lines/sec to 20 lps on all my Items that gather log data, The Zabix text write cache & History write cache start decreasing slowly, basically unable to write the data out to the DB quick enough.

I have tried increasing the server size, increase the database memory & # of cpus (I am running all this with an Amazon c1.medium EC2 instance and m1.small instance, and have increased the EC2 instance to a c1.xlarge and RDS to m1.large) and have not seen ANY improvement at all. The larger Amazon instances I have tried each have roughly 4x the memory and 4x the # of cores.

Is there any way to see what the issue is? Why are there not more dbsyncers actively writing data and not all sleeping? The Amazon RDS mysql instance has all the defaults which are for the most part set it and forget it, and I have tried tweaking the Zabbix Server parameters and nothing makes any difference. Zabbix acts almost as if it is single-threaded, and is not scaling according to the # of cpus (neither server cpus nor database/RDS cpus).

Thanks for any help you can provide.

Memmove may work quite slow in case of large (100K-1M) number of items.

Available in pre-1.8.3 in r12188.

Available at pre1.8.3, revision 11579

Available in pre-1.8.3 in r11487.

Available in pre-1.8.3 in r11271.

ZBXNEXT-279

1. what about trigger editing form - is that feasible to do the same in there, would that be done in the scope of this issue or not ?
2. it would be nice if host name and item name could be somehow distinguished - otherwise they blend together too easily

1. ye, forgot about triggers.
2. somehow?

2. well, font colour, some symbols... not sure. currently it is almost impossible to visually identify host vs item

3. slightly different issue, but exposed by this one... have a template that is linked to another template which is set to "deny" for the current user. edit a trigger in that template :

Host does not exist.Check expression part starting from '

>4'

3.1. space missing before "Check";
3.2. this works with items, so should work with triggers as well...
3.3. operation is not atomic - it changes trigger for the hosts user has permission, but not for "deny" ones.

permission problem reported as ZBX-2499, changes in this issue good to merge.

branches/1.8 12492

fixed

seems to work as expected in the dev branch, rev 11982.

branches/1.8 11987

this was implemented in 1.8.3

Debian 5.0

from the downstream report :
"One of the requirements for TCP/IP ports usage in a vserver is that the port isn't bound to 0.0.0.0 in the host, so you typically bind to only the IPs you are interested in. So I wanted to do a bind on the public IP and another one to the private IP."

I moved it to feature requests. I do not see any bug here.

Available in pre-1.8.3 in r12472.

If ListenIP configuration parameter is not specified, daemons crash.

Fixed in pre-1.8.3 in 12504.

Fixed compilation on Windows platforms in r12733.