Best Practices for color schemes?

[CWempe]

When creating color schemes I am always unsure what colors to use.

Maybe someone (or the community) could write some best practices or recommendations.

For example:

• error should be red,,bold
• debug should black,yellow,bold
• timestamps at the beginning of the line should be white,,bold

What do you think? Would this be useful or is any log file so different that each needs a unique color theme?

[CWempe]

As a starting point we could base this on the eight Syslog Severity Levels.

Value	Severity	Keyword	Deprecated keywords	Description	Condition
0	Emergency	emerg	panic[9]	System is unusable	A panic condition.[10]
1	Alert	alert		Action must be taken immediately	A condition that should be corrected immediately, such as a corrupted system database.[10]
2	Critical	crit		Critical conditions	Hard device errors.[10]
3	Error	err	error[9]	Error conditions
4	Warning	warning	warn[9]	Warning conditions
5	Notice	notice		Normal but significant conditions	Conditions that are not error conditions, but that may require special handling.[10]
6	Informational	info		Informational messages	Confirmation that the program is working as expected.
7	Debug	debug		Debug-level messages	Messages that contain information normally of use only when debugging a program.[10]

Here is my first suggestion (using Cisco IOS logs):

I think in general we could use colors in pairs instead of using 8 different colors. But DEBUG could be colored different, because you might want to see this first. That is why you enabled debugging in the first place. And to notify the user that debug is still on. ;)

[folkertvanheusden]

This looks great, I agree.

On Sat, Nov 4, 2023 at 2:42 PM Christoph Wempe @.***> wrote:

As a starting point we could base this on the eight Syslog Severity Levels https://en.wikipedia.org/wiki/Syslog#Severity_level. Value Severity Keyword Deprecated keywords Description Condition 0 Emergency emerg panic[9] System is unusable A panic condition.[10] 1 Alert alert Action must be taken immediately A condition that should be corrected immediately, such as a corrupted system database.[10] 2 Critical crit Critical conditions Hard device errors.[10] 3 Error err error[9] Error conditions 4 Warning warning warn[9] Warning conditions 5 Notice notice Normal but significant conditions Conditions that are not error conditions, but that may require special handling.[10] 6 Informational info Informational messages Confirmation that the program is working as expected. 7 Debug debug Debug-level messages Messages that contain information normally of use only when debugging a program.[10]

Here is my first suggestion (using Cisco IOS logs):

[image: image] https://user-images.githubusercontent.com/1270359/280469886-f3846e20-aa5d-4b1c-bbe6-9ed568c4c8a5.png

I think in general we could use colors in pairs instead of using 8 different colors. But DEBUG could be colored different, because you might want to see this first. That is why you enabled debugging in the first place. And to notify the user that debug is still on. ;)

— Reply to this email directly, view it on GitHub https://github.com/folkertvanheusden/multitail/issues/24#issuecomment-1793447600, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUN5IW3LRXSKSZDN3LD6NG3YCZA2DAVCNFSM6AAAAAA62BA6XSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGQ2DONRQGA . You are receiving this because you are subscribed to this thread.Message ID: @.***>