PATCH: Bulk Fixes / Changes For 1.1.7

[James Wells]

Greetings,

Enclosed is my bulk patch set upgraded for 1.1.7. In addition to the changes listed in PATCH: Bulk Fixes / Changes For 1.1.6, this patch also contains a small change, produced by Palmertree to provide a very preliminary support for sending emails as high priority, as well as all of my previous fixes / changes.

Finally, this patch reintroduces Sarek's PATCH: External scripts system. This allows you to create server side scripts that act just like items, and can even be included in a hosts item list.

At present, I am about 60% complete on the documentation of the frontend, and expect to complete it within the next 2 weeks or so. Once that is complete, I will begin migrating these changes, fixes over to the 1.3.x / 1.4.x branches.

[Alexei]

James, please, note that support of external checks is already intergrated into 1.3.x.

[James Wells]

Just saw that on the Todo list.

That will be a huge boon for people if it makes it in to the 1.4.x branch. I know we will be using it.

[welkin]

What do i have to keep in mind when updating an already running zabbix?
Same as in he Bulk Patch for 1.1.6?

to use this patch to it's fullest, against a populated Zabbix DB, you will need to execute the following MySQL (Or other commands for other DBs) commands;
Code:

alter table `items` change `key_` `key_` VARCHAR(255) NOT NULL; alter table config add ackduration int(4) DEFAULT '1800' NOT NULL; alter table alerts add ackuntil int(4) DEFAULT '0' NOT NULL;



Additionally, to take advantage of the new improved Server Status, you will need to edit a new configuration file called server.inc.php, in the Zabbix UI include directory. This file contains a couple of new configuration entries that are used to gather status using native Zabbix tools. Please read the thread posted at PATCH: Improved Server Status In Reports for further details on using this patch

[James Wells]

What do i have to keep in mind when updating an already running zabbix?
Same as in he Bulk Patch for 1.1.6?

Yes, if you are already using my 1.1.6 bulk patch, then your DB changes are already in place. If that is the case, then you simply modify the UI's db.inc.php and server.inc.php as you did for the 1.1.6 bulk patch, re-compile and deploy your binaries, and go.

If, on the other hand, you were not using my previous bulk patches then you will need to edit the include/server.inc.php, under the Zabbix UI, then you will need to alter your database using the SQL statements.

[vrtareg]

Hi

This is a great patch.
Very nice colors improvements!!!!!!!!
Can this patch included in future 1.1.x releases ?

Regards
Areg

[inko_nick]

A little problem

Great job. Several days ago i use multi-patch for zabbix 1.1.7. All works just fine but i have a little problem.
Now, when i try to create a new trigger i receive

Warning. Field [priority] is not integer

Can you please help me, i'm newbie in scripting and php.
Thanx

[inko_nick]

Sorry.
It's Ok.

Was my fault.

[glut0r]

Greetings,

Enclosed is my bulk patch set upgraded for 1.1.7. In addition to the changes listed in PATCH: Bulk Fixes / Changes For 1.1.6, this patch also contains a small change, produced by Palmertree to provide a very preliminary support for sending emails as high priority, as well as all of my previous fixes / changes.

Finally, this patch reintroduces Sarek's PATCH: External scripts system. This allows you to create server side scripts that act just like items, and can even be included in a hosts item list.

At present, I am about 60% complete on the documentation of the frontend, and expect to complete it within the next 2 weeks or so. Once that is complete, I will begin migrating these changes, fixes over to the 1.3.x / 1.4.x branches.

would you consider safe_mode fixes in your bulk patch ? It would make zabbix-frontend display correct status even if running with safe_mode=on.

[glut0r]

This patch kicks ass I missed features such as creating trigger directly by hitting button from inside of item definition. Great
Clone item would be great, but since 1.4 is supposed to have this, I wait.

[James Wells]

would you consider safe_mode fixes in your bulk patch ? It would make zabbix-frontend display correct status even if running with safe_mode=on.

I like the fsockopen trick. Will probably keep the configuration portion of the server status, but remove the call to zabbix_get, and just use the fsockopen instead. Basically, mixing what I have now with what you have shown. This would give me the ability to retain the status display, which we use where I work, and the remote checking ability that others use.

[glut0r]

I find 1h default graph grid highly annoying. It's not hard to fix it digging in .php scripts, but, at last it was true in 1.1.6, appropiate values were hardcoded inside the source and not moved into configurable variables.

I'd rather see 24h instead of 1h which is totally unreadable. The very first thing I ever do watching graphs/screens is changing default.

Would you possibly add these fixes in your patch? If you think it is a thing to fix of course . I hope I'm not the only one who finds 1h graphs useless though.

[tronite]

Hi

This is a great patch.
Very nice colors improvements!!!!!!!!
Can this patch included in future 1.1.x releases ?

Regards
Areg

I think patches are obviously always included in future releases unless there is a totally different way that some bug is fixed.

[tronite]

This patch kicks ass I missed features such as creating trigger directly by hitting button from inside of item definition. Great
Clone item would be great, but since 1.4 is supposed to have this, I wait.

Lucky me I just started using zabbix on 1.4. Golden ages