Use Slog logger

[mehdihadeli]

• A Comprehensive Guide to Structured Logging in Go
• Creating a pretty console logger using Go's slog package
• log/slog: structured, leveled logging golang/go#56345
• https://github.com/lmittmann/tint
• https://github.com/neilotoole/slogt
• https://github.com/gookit/slog
• https://github.com/samber/slog-multi
• https://github.com/golang-cz/devslog
• https://github.com/go-slog/awesome-slog

[Alan-MQ]

I wanna try this one too, but I'm not sure if I am running this project correctly~~,
just run cmd/app/main.go from catalog_read_service, write_service and order_service?

[Alan-MQ]

And I notice we will intergate ELK to this project, so we might wanna Use Slog before we introduce ELK right? and by the way, intergate ELK need someone fully understand this project right? about how fx are working here and event driven , message queue all that stuff~~~

[Alan-MQ]

And I notice we will intergate ELK to this project, so we might wanna Use Slog before we introduce ELK right? and by the way, intergate ELK need someone fully understand this project right? about how fx are working here and event driven , message queue all that stuff~~~

try to run this project with this method and I got something like this

but , when I make unit-test locally all tests passed. that means the docker enviroment was nothing wrong right?

[mehdihadeli]

Yes, slog is built structured logging in go 21.0, so it is better we switch to this library. Maybe we have to upgrade the project to go 21.0 at first. Maybe in a separated issue or pull request.
Yes, first we should use slog after that we integrate that with ELK and kibana

[mehdihadeli]

And I notice we will intergate ELK to this project, so we might wanna Use Slog before we introduce ELK right? and by the way, intergate ELK need someone fully understand this project right? about how fx are working here and event driven , message queue all that stuff~~~

try to run this project with this method and I got something like this

but , when I make unit-test locally all tests passed. that means the docker enviroment was nothing wrong right?

This is a temp docker container that use by go-testcotainer library for my integration and end-to-end tests, it should be ephemeral and after running tests it should be destroyed. 65027:27017 is a testcontainer for MongoDB.
Yes, it is fine, no problem. Just some logging to destroy containers, I think so. Maybe after destroy container by testcontainer we lost the connection for mongo, and we get this error

[mehdihadeli]

Could you first upgrade to version 21 at first #81 ?

[Alan-MQ]

ok, so I will look up all this parpers you mentioned on the top , and come up with a plan about how to use slog, but at some point , I'm gonna need to run this project correctly to see the log right ? is there any doc on how should I run this project?

[Alan-MQ]

Could you first upgrade to version 21 at first #81 ?

sure

[mehdihadeli]

Thanks

[mehdihadeli]

For migrating to slog, you can create an abstraction like my zap abstraction. at the end all of this abstraction like zap, logrus, ... will implement logger interface and we use logger interface totally in the app

[Alan-MQ]

ok， I will check it out first.