Replace log with structured logging log/slog #31

Closed
opened 2024-09-04 13:04:34 +02:00 by kamikazechaser · 5 comments

This is required to collect and process logs for alerting. Ideally go-vise also does the same if go-vise logging is activated in this project.

fmt.Printf statements should also be replaced at some point.

This is required to collect and process logs for alerting. Ideally go-vise also does the same if go-vise logging is activated in this project. fmt.Printf statements should also be replaced at some point.
kamikazechaser added the
Kind/Feature
Kind/Enhancement
Priority
Low
refactor
easypeasy
labels 2024-09-04 13:04:34 +02:00
Owner

we have a logger in go-vise/logging - does it suffice? @kamikazechaser

we have a logger in go-vise/logging - does it suffice? @kamikazechaser
Author
Owner

Looks good. However, the existing one go-vise/logging could be implemented as a slog Handler. By accepting slog.Logger, anyone can bring their own logger.

I can bring this feature to go-vise if you like the idea.

Looks good. However, the existing one `go-vise/logging` could be implemented as a [slog Handler](https://go.dev/blog/slog). By accepting slog.Logger, anyone can bring their own logger. I can bring this feature to go-vise if you like the idea.
Owner

I can bring this feature to go-vise if you like the idea.

@kamikazechaser sure, thanks! I have added an issue for it here: https://defalsify.org/issues/vise/2dc45a02-36de-42d3-9b20-4305a49f3d9b.html

> I can bring this feature to go-vise if you like the idea. @kamikazechaser sure, thanks! I have added an issue for it here: https://defalsify.org/issues/vise/2dc45a02-36de-42d3-9b20-4305a49f3d9b.html
Owner

@kamikazechaser are you still on this, or should I take it? I know u busy

@kamikazechaser are you still on this, or should I take it? I know u busy
Owner

we have slogging but still need e.g. json output format, will make different issue for that

we have slogging but still need e.g. json output format, will make different issue for that
lash closed this issue 2024-12-31 10:36:41 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: urdt/ussd#31
No description provided.