You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
During the viewing of logging with multiple processes in a pod, there are automatically picked randomized colors used for the process names. Sometimes these are unreadable due to the skin used, but cannot be altered in the skin settings. This also goes for ERROR level logging (java in this case, might be for WARN as well or other languages), where the entire stack trace is a dark red. Sidenote: when enabling timestamps, only the first line is red, not the entire stack trace.
Describe the solution you'd like
I would like to have a skin setting where I can define a(n array of) color(s) used for the process indicators (randomly or sequentially picked) and stack traces or loglevel entries. There should be defaults defined to make sure this doesn't break if they're not present or have a value that is invalid (ie. like it is now).
Describe alternatives you've considered
I checked on Slack first to see if I was doing something wrong, or maybe the source of the coloring would be somewhere else.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
During the viewing of logging with multiple processes in a pod, there are automatically picked randomized colors used for the process names. Sometimes these are unreadable due to the skin used, but cannot be altered in the skin settings. This also goes for ERROR level logging (java in this case, might be for WARN as well or other languages), where the entire stack trace is a dark red. Sidenote: when enabling timestamps, only the first line is red, not the entire stack trace.
Describe the solution you'd like
I would like to have a skin setting where I can define a(n array of) color(s) used for the process indicators (randomly or sequentially picked) and stack traces or loglevel entries. There should be defaults defined to make sure this doesn't break if they're not present or have a value that is invalid (ie. like it is now).
Something like:
Possibly not nested in
indicator
.Describe alternatives you've considered
I checked on Slack first to see if I was doing something wrong, or maybe the source of the coloring would be somewhere else.
Additional context
The text was updated successfully, but these errors were encountered: