admin
25-04-2009, 13:00
Dear All,
We have just released a new version of the Java-monitor monitoring tool. Unfortunately we had to delete the historical data for the past two days. There were too many changes in the schema to be able to migrate the data quickly, so it was this or two hours of downtime. Sorry for the data.
The most notable change in this release is the newer schema. We removed some extraneous columns from the database, trimmed the database indexes down and changed the janitor thread policies. The effect of this is much faster performance on generating the graphs.
We added some redundancy when storing the data in the database. This makes it easier to delete historic data. Funny that all database design classes I took stressed that normalization is king, while for this particular type of database design it is better to have some redundancy. In this schema, it breaks the dependency between two tables, making it easier to clean up.
We now automatically delete hosts that have not received data for more than a month. This will clean up your views and cuts back on the amount of data we have to maintain in the database.
The probe should now detect your Jetty servers and their versions. You have to install the new probe for this to work.
The probe also has a shorter back-off time. This time was reduced to 5 minutes from 15.
Kees Jan
We have just released a new version of the Java-monitor monitoring tool. Unfortunately we had to delete the historical data for the past two days. There were too many changes in the schema to be able to migrate the data quickly, so it was this or two hours of downtime. Sorry for the data.
The most notable change in this release is the newer schema. We removed some extraneous columns from the database, trimmed the database indexes down and changed the janitor thread policies. The effect of this is much faster performance on generating the graphs.
We added some redundancy when storing the data in the database. This makes it easier to delete historic data. Funny that all database design classes I took stressed that normalization is king, while for this particular type of database design it is better to have some redundancy. In this schema, it breaks the dependency between two tables, making it easier to clean up.
We now automatically delete hosts that have not received data for more than a month. This will clean up your views and cuts back on the amount of data we have to maintain in the database.
The probe should now detect your Jetty servers and their versions. You have to install the new probe for this to work.
The probe also has a shorter back-off time. This time was reduced to 5 minutes from 15.
Kees Jan