-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Lets say you want a hypothetical log with message id ZWET0123 to show up in the syslog, but the message looks like this
2025-01-16 14:05:56.911 <ZWEAGW1:parallel-5:16842795> �[35mZWESVUSR�[0;39m �[36mDEBUG�[0;39m ((o.z.a.g.c.NettyRoutingFilterApiml)) ZWET0123 Using client with keystore true
The current logic of the launcher syslog messages is to take the matching line, truncate to 126 characters, and put that in the log.
But that would mostly just show the timestamp & misc information, and very little of the actual message itself.
It shouldn't be hard to trim the content before the match, so that the syslog could look like this instead
ZWET0123 Using client with keystore true
Changing that behavior could be seen as disruptive (though, i dont think the syslog behavior is documented and should be...)
It could be that this behavior is introduced as an option co-existing with the existing behavior.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status