Replies: 4 comments 2 replies
-
Good question. |
Beta Was this translation helpful? Give feedback.
-
This will require each and every component to provide custom properties, that's not really useful. e.g. the slf4j simple logger has the following properties: https://www.slf4j.org/api/org/slf4j/impl/SimpleLogger.html that would be useful here is well. |
Beta Was this translation helpful? Give feedback.
-
External configuration of each There is also Configuration Admin which can be used to configure LoggerContext (see https://docs.osgi.org/specification/osgi.core/8.0.0/service.log.html#d0e54441) We do have built-in configuration property |
Beta Was this translation helpful? Give feedback.
-
@tjwatson thanks for the insight, I know this could be done through config admin / logger admin, I'm just more searching for something that is used as defaults if no such configuration exits. For example I currently investigate if we can include slf4j-osgi but this might produce a lot of log outputs, so people will instantly complain about "logspam", so an easy to use (e.g. adding a property to eclipse.ini) would be good, while telling them to fetch OSGi service and doing something in code will most probably be "to complex" :-) |
Beta Was this translation helpful? Give feedback.
-
The only option I could found so far is
eclipse.log.level
orlog.threshold
mentioned but this configures everything on the global level, but I like to control this on "logger" level (e.g. per bundle), so is there a way using system-properties/config files/ ... or is this a missing feature?Beta Was this translation helpful? Give feedback.
All reactions