Globally raising the Update Interval

[pnicolosi78]

Is there an easy way to change the Update Interval? Currently I have it set to low and I want to raise it. Since Zabbix is SQL based, couldn't it be done through a script of some sort? Or is there somewhere on the server I can update it?

I'm using Zabbix 1.0 monitoring about 60-70 hosts, all of which have about 20 or more items being monitored on each server. It'd be a real pain in the butt to have to manually change them all. Not to mention time consuming.

[Mark Ramm-Christensen]

Is there an easy way to change the Update Interval? Currently I have it set to low and I want to raise it. Since Zabbix is SQL based, couldn't it be done through a script of some sort? Or is there somewhere on the server I can update it?

I'm using Zabbix 1.0 monitoring about 60-70 hosts, all of which have about 20 or more items being monitored on each server. It'd be a real pain in the butt to have to manually change them all. Not to mention time consuming.

Currently there is no way to do this in ZABBIX itself, but you are right you could write a script to do it. The trick will be that you 60-70 hosts are probably configured to watch multiple items with different update times per item -- so your script would have to deal with all of that.

--Mark

[pnicolosi78]

wouldn't it just be one column in the database? Or do I have to worry about updating other fields along with it?

[pnicolosi78]

I found out where it is. I used knoda to connect to the MySQL database on my Zabbix server. Then, I checked the items table and found a column called 'delay'. I created a query to update all the items in that column to 300. Effectively changing the amount of time between updates to 5 minutes. Works fine now.

[cooper]

to update with a little more precision next time you could go with something like:

UPDATE items SET delay=xx WHERE key_="disktotal[/usr]";

That will set all the disktotal[/usr] items to check every xx seconds. This way you'll have a little more control next time.

cooper

[pnicolosi78]

Doesn't apply to my situation. My company doesn't monitor Linux Servers or Workstations. They just monitor Windows Servers and Network Devices. So I don't think the extra condition is necessary.

[cooper]

Doesn't apply to my situation. My company doesn't monitor Linux Servers or Workstations. They just monitor Windows Servers and Network Devices. So I don't think the extra condition is necessary.

It doesnt matter what you monitor. The WHERE condition is used to cut down the number of records that you are updating. I used disktotal[/usr] as an example as a lot, of the people on this board are monitoring unix. Key_ is any of the item keys listed at http://www.zabbix.com/manual_config_items.php. It could have just as easily been

UPDATE items SET delay=xx WHERE key_="disktotal[c:]";

Which would set all the items that monitor disktotal[c:\] to xx seconds.

You made your update with a saw. I was pointing out how to do it with a scalpel.

[pnicolosi78]

true, but I was just looking to update all of the items, not just specific ones. Your way does help if I just needed to update certain items. I would definately of used WHERE if it was needed. But needless to say, you are right, I was sawing through it, your method is a bit more precise. THanks for the help