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.

Sign up for GitHub

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

Jump to bottom

syslog severity mapping problem #142

Closed
xjplke opened this issue Apr 3, 2024 · 0 comments
Closed

syslog severity mapping problem #142

xjplke opened this issue Apr 3, 2024 · 0 comments
Assignees
@inhere
Labels
bug Something isn't working enhancement New feature or request resolved

Comments

@xjplke
Copy link

xjplke commented Apr 3, 2024

slog/handler/syslog.go

Line 60 in 70031a7

return h.writer.Info(string(bts))

All slog Level are set to syslog severity Info.
Suggest slog Level to syslog severity as sub：
PanicLevel -> LOG_EMERG
FatalLevel -> LOG_CRIT
ErrorLevel -> LOG_ERR
WarnLevel -> LOG_WARNING
NoticeLevel -> LOG_NOTICE
InfoLevel -> LOG_INFO
DebugLevel -> LOG_DEBUG
TraceLevel -> LOG_DEBUG
@inhere inhere added the bug Something isn't working label Apr 7, 2024
@inhere inhere self-assigned this Apr 7, 2024
@inhere inhere added the enhancement New feature or request label Apr 7, 2024
@inhere inhere closed this as completed in 1b25cfd Apr 7, 2024
@inhere inhere added the resolved label Apr 7, 2024
@yermulnik yermulnik mentioned this issue May 2, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@inhere inhere

Labels
bug Something isn't working enhancement New feature or request resolved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xjplke @inhere