celix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Broekhuis <a.broekh...@gmail.com>
Subject Re: [jira] [Created] (CELIX-87) Log writer to syslog
Date Thu, 03 Oct 2013 06:42:06 GMT

2013/10/2 Gerrit Binnenmars <gerritbinnenmars@gmail.com>
>> Regarding the properties:
>> The log service itself doesn't have any properties defined in the spec.
>> But
>> looking at Felix it probably makes sense to have some to specify the
>> maximum number of messages to keep in memory and to specify wether debug
>> messages should be stored.
>> These properties only influence the storage of entries, and has nothing to
>> do with subscribed listeners, so even if debug messages are not stored
>> they
>> are still send to the listeners.
>> All other properties can be handled in the specific listener
>> implementation. In other words, the LogService is only meant for creating
>> log entries. With the ReaderService and Listeners it is possible to
>> process
>> those logs in a specific way best suited for the actual user.
> So, the LogWriter needs a log_level property to do some filtering.

Seeing as there is already a LogWriter in Celix I think the name is a bit
misleading. But you are correct, the component using the LogReaderService
(or implementing the LogListener) is responsible for these kind of things.

>> So while I do think it is interesting for Celix to have a syslog writer, I
>> am not sure if the specific request for filtering will fit in a generic
>> solution. It might be better to implement this writer for your specific
>> use
>> case. A good example of a listener is the LogWriter bundle which writes to
>> standard out.
> Agree with you, we can work on the LogWriter as a new bundle. I think it
> is still useful to add this to Celix for other users.

Sounds good to me. Could you update the Jira entry so that it concerns the
(lack of) logging of the framework and usage of the LogService?


Met vriendelijke groet,

Alexander Broekhuis

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message