Hello again. I have had a look at the lines that have an unsuitable thread name, and I can't identify a unique logger. Lines from commands "log:log" have a logger "core", but other commands have multiple loggers, and I don't see any way to configure a pattern without the thread name for all these lines.
Any suggestions .? Thanks again. Regards. Le mer. 1 oct. 2025 à 15:44, Matt Pavlovich <[email protected]> a écrit : > Your logging configuration must be using a pattern that includes the > thread name in the log output. You can remove that macro, or configure a > separate log appender for the packages you want to filter and give that a > different logging pattern without the thread macro. > > -Matt > > > On Oct 1, 2025, at 5:35 AM, Ephemeris Lappis <[email protected]> > wrote: > > > > Hello. > > > > We need to use the Karaf's shell "log" command to trace actions during > some deployment opérations.. > > > > We've seen that the thread name using the "log:log" command is the > command itself, producing very big lines in the log file. > > > > Example : > > admin@root()> log:log --level WARNING "A very very long text..." > > 12:29:39.362 WARN [pipe-log:log --level WARNING "A very very long > text..."] A very very long text... > > > > The thread name is "pipe-log:log --level WARNING "A very very long > text..."" > > > > In reality, messages may be actually bigger, since we want to trace very > detailed information about the current deployments. > > > > Is there any way to avoid this ? > > > > Thanks in advance for your help. > > > > Regards. > >
