|
Event Report - %s
|
|
Please rename either your config.php.dist or config_local.php.dist files in the syslog directory, and change setup your database before installing.
|
|
Syslog 2.0 Requires an Entire Reinstall. Please uninstall Syslog and Remove all Data before Installing. Migration is possible, but you must plan this in advance. No automatic migration is supported.
|
|
What upgrade/install type do you wish to use
|
|
When you have very large tables, performing a Truncate will be much quicker. If you are concerned about archive data, you can choose either Inline, which will freeze your browser for the period of this upgrade, or background, which will create a background process to bring your old syslog data from a backup table to the new syslog format. Again this process can take several hours.
|
|
Background Upgrade
|
|
Database Storage Engine
|
|
MyISAM Storage
|
|
Database Architecture
|
|
Traditional Table
|
|
Partitioned Table
|
|
Choose how many days of Syslog values you wish to maintain in the database.
|
|
Partitions per Day
|
|
Select the number of partitions per day that you wish to create.
|
|
%d Per Day
|
|
Upgrade
|
|
Syslog %s Advisor
|
|
You can also select the retention duration. Please keep in mind that if you have several hosts logging to syslog, this table can become quite large. So, if not using partitioning, you might want to keep the size smaller.
|
|
You can also set the MySQL storage engine. If you have not tuned you system for InnoDB storage properties, it is strongly recommended that you utilize the MyISAM storage engine.
|
|
Syslog %s Settings
|
