|
From: James O. <jo...@re...> - 2004-09-01 16:45:16
|
Hi all, Ok, I got the deletion policy issue resolved. For whatever reason the perfdata_delete_policy table was not populated, and once the two defaults were in there it started working... However it was a bit too late ;) I discovered that my innodb file had grown to 13G, and one of the tables is now totally unresponsive (perfdata_service_bin). So the question that I have is if I want to have graphical data for these metrics over at least the last year, if not longer, what data would I have to keep? What tables are used for generating the graphs? Secondly, I have a relatively small environment that I am monitoring with nagios right now (in the neighborhood of 200 machines) and I have only set up about 10% of them so far. I have only had perfparse running for about a month and a half and already generated a 13G database file... if I specify the no-raw option will that drastically cut down on the amount of data being stored? Of course, if I can set short times on the delete policies and still get graphs over the time period that I need then this becomes a non-issue. The third question is if anyone has had success using the file_per_table option with innodb and mysql and perfparse? It seems like it would be easier to manage the file sizes with separate files for each table. Thanks, James |