MonitorWare Knowledge Base

Another question related to this one:
http://www.phplogcon.org/index.php?name ... &p=191#191

Should filtering be done in the "LogStream Facility" or in the frontend?
I think it would make sense to do filtering in the LogStream Facility as filtering can be converted based on the underlaying syslog source. For example if we have a MYSQL Database, it would make sense to have the filtering done in a SQL Query.

If we go this way, we need to define a filter interface as well.

Definitely in the logstream - there already is a filter class in the uml for that. It's pretty important that we get the new source repository up so that we can share these documents. Michael will probably also upload them to the server very soon.

The current filter interface in UML is *very* underspecified. It just tells there is one. I tend to use the same approach you proposed for the properties. That is a structure that holds

* property to be filtered on
* filter operation
* value to match

Of course, this does not yet include boolean operations, we need to think a bit about that part. But for starters, such a simple structure plus an implied AND could bring is quite far...

Rainer

Ok simple filter operations would be fine for the beginning.

The plus (IMHO) is that the upper level app (still no name for it?) does not need to care about filtering at all. Except, of course, providing abilities to set filters and display which one is active.