In Summary: SMOOTH
About the Zbx environment...
I did the upgrade a week ago now. I'm not very active with Zabbix and since it was installed the feature-lists have grown. A lot of the new features I don't use. I didn't record any stats prior to the upgrade because I didn't plan on posting this. I was running 1.8.<i don't recall> before and installed the deb package for 2.0 (2.0.2+dfsg-3).
As for the database schema, mine is very old... it has been upgraded to all major versions since about 1.0. I believe I even ran a beta for awhile somewhere in the past (maybe v1.3, I don't recall) that required some manual schema repairs. I'm currently running 5.3.7-mariadb116~squeeze for my DB server. No configuration changes have been made to mysql. I left everything as they were.
After the upgrade, some scripts broke because they access the database directly. Once I figured out the necessary query changes, my old scripts were working fine again.
A week ago, the upgrade was done. The only metric I can report on is the CPU usage which has gone from about 5.0 average to 8.5 average.
Also, I just checked the "Required server performance, new values per second" report and it says 18.46. I have no idea really what this value means except people have posted it as a metric for load. 99% of my the items I have running are set to to a type of active.
Oh, one last thing I can think of. I didn't upgrade the proxies (we don't rely on them for anything much) and they appear to be working fine even though the docs say they need to be v2. Maybe they are actually not working and they are broken?
...I haven't checked, but my guess is there must be one proxy out there with nodata triggers. Heh.
-Brendon
About the Zbx environment...
I did the upgrade a week ago now. I'm not very active with Zabbix and since it was installed the feature-lists have grown. A lot of the new features I don't use. I didn't record any stats prior to the upgrade because I didn't plan on posting this. I was running 1.8.<i don't recall> before and installed the deb package for 2.0 (2.0.2+dfsg-3).
As for the database schema, mine is very old... it has been upgraded to all major versions since about 1.0. I believe I even ran a beta for awhile somewhere in the past (maybe v1.3, I don't recall) that required some manual schema repairs. I'm currently running 5.3.7-mariadb116~squeeze for my DB server. No configuration changes have been made to mysql. I left everything as they were.
After the upgrade, some scripts broke because they access the database directly. Once I figured out the necessary query changes, my old scripts were working fine again.
A week ago, the upgrade was done. The only metric I can report on is the CPU usage which has gone from about 5.0 average to 8.5 average.
Also, I just checked the "Required server performance, new values per second" report and it says 18.46. I have no idea really what this value means except people have posted it as a metric for load. 99% of my the items I have running are set to to a type of active.
Oh, one last thing I can think of. I didn't upgrade the proxies (we don't rely on them for anything much) and they appear to be working fine even though the docs say they need to be v2. Maybe they are actually not working and they are broken?
...I haven't checked, but my guess is there must be one proxy out there with nodata triggers. Heh.-Brendon
