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

No color highlight in logs #13699

Closed
julienrbrt opened this issue Oct 31, 2022 · 8 comments
Closed

No color highlight in logs #13699

julienrbrt opened this issue Oct 31, 2022 · 8 comments
Labels
T: Dev UX UX for SDK developers (i.e. how to call our code)

Comments

@julienrbrt
Copy link
Member

julienrbrt commented Oct 31, 2022

Summary of Bug

No color highlight in logs on using simd on main:
image

v0.45/v0.46
image

I suspect #13236 to be the reason (however I have not verified). Is it intended? If so we can close this.

Version

main

Steps to Reproduce

simd start

@tac0turtle
Copy link
Member

Since we removed zero log in favor of the previous filter logging we lost the coloring. To get the coloring back we would need to rewrite the zerlogger with filtering in mind

@alexanderbez
Copy link
Contributor

Since we removed zero log in favor of the previous filter logging we lost the coloring. To get the coloring back we would need to rewrite the zerlogger with filtering in mind

Yup (RIP Zerolog)

@tac0turtle tac0turtle added the T: Dev UX UX for SDK developers (i.e. how to call our code) label Nov 15, 2022
@julienrbrt
Copy link
Member Author

Can you tell me what are the requirements of the logger? Is it mainly filtering?
How filtering works btw, how to use it?

@tac0turtle
Copy link
Member

tac0turtle commented Dec 16, 2022

here is the filtering we use: https://github.com/tendermint/tendermint/blob/main/libs/log/filter.go. There is a way to do this with zero logger, just requires some changes

Also I don't have color logging with 0.45 on my nodes, so think this is a low priority thing

@robert-zaremba
Copy link
Collaborator

Colored logging should be optional (definitely not enforced)

@alexanderbez
Copy link
Contributor

TBH, this typically is automatically handled for you via the logging library. E.g. logs are typically written in either structured format (i.e. JSON) or human-friendly (i.e. text). When it's text, it should automatically be colored.

@robert-zaremba
Copy link
Collaborator

When it's text, it should automatically be colored.

agree, but it should be optional. Typical use case: redirecting logs textual logs.

@julienrbrt
Copy link
Member Author

Superseded by #14967

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: Dev UX UX for SDK developers (i.e. how to call our code)
Projects
None yet
Development

No branches or pull requests

4 participants