Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable colors related to pod processes and error entries in logs #935

Open
JayKus opened this issue Nov 10, 2020 · 0 comments
Open

Comments

@JayKus
Copy link
Contributor

JayKus commented Nov 10, 2020




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:

k9s:
  views:
    logs:
      indicator:
        processes: [ 'color1', 'color2', 'color3', 'color4' ]
        loglevel:
          warn: color5
          error: color6

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
image (8)
image (7)
image (9)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant