Hi Alexei, (you're still the sole developer on this?)
I just found that zabbix-1.1alpha7 has a rather severe bug.
When you restart mysql (by stopping and then starting it) zabbix_serverd dies completely.
IMHO zabbix should:
1) not die if mysql isn't accessible - so it can start using mysql when it's available again, automatically.
2) surveilance data is way tooo important to be lost, just because mysql temporarily isn't available. IMHO it would be best if you could configure a "log directory" - where zabbix could simply store the sql-queries it would have performed (unless they are select's - which change the insert statement, then it must be done otherwise) so the missed transactions can be replayed, once mysql is online again.
nr. 2 could be implemented rather simply, and would be really great IMHO.
I just found that zabbix-1.1alpha7 has a rather severe bug.
When you restart mysql (by stopping and then starting it) zabbix_serverd dies completely.
IMHO zabbix should:
1) not die if mysql isn't accessible - so it can start using mysql when it's available again, automatically.
2) surveilance data is way tooo important to be lost, just because mysql temporarily isn't available. IMHO it would be best if you could configure a "log directory" - where zabbix could simply store the sql-queries it would have performed (unless they are select's - which change the insert statement, then it must be done otherwise) so the missed transactions can be replayed, once mysql is online again.
nr. 2 could be implemented rather simply, and would be really great IMHO.
Comment