Log watchers may be configured

[ejhernandez@…]

Currently, the eBox log event watchers may watch the new log lines without filtering.

It could be cool to be able to manage filters (add, edit, remove) to be notify from.

The main issue is to generate the model when a new model has been developed and the migration that may appear when developing a LogObserver which may change its tableInfo, that is, its database schema.

[ejhernandez@…]

(In [8874]) Starting autogeneration models from LogWatcherFiltering model template when a new log domain is added refs #883

[ejhernandez@…]

(In [8879]) * Added configuration for log watchers. Now, you can enable and disable if you want to be notified when a log from a domain has happened.

• This log line must match a series of filters you may add to the log watcher configuration filter
• These filters are queried in order and the results appended
• EventConfigurationModels? may have submodels which must be returned by subModels method
• menuNamespace now takes index into account
• Warns if the configuration is not correct by enabling the log watcher but no log watcher domain is enabled and vice versa

All refs #883

[ejhernandez@…]

(In [8885]) Fixing bug by passing dates to search method. Storing the last queried time on gconf state instead of using a file. Missing use refs #883

[ejhernandez@…]

(In [8890]) * Missing semi-colon

• Fixing bug with the date returned by localtime
• Does not compute when no result are found by count query in search
• Match against value instead of printableValue on querying if the log watcher is enabled
• Delete trailing spaces to make human readable text

closes #883 (spent 9.75)