You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The downloader now sports structure logging as its focus shifted towards an automation tool.
The aggregator always was thought as such a tool.
Therefore the aggregator should use the structured logging, too.
The text was updated successfully, but these errors were encountered:
This PR adds structured logging for the aggregator service. Currently, only the text handler is used, but I can extend this to use the JSON handler as well. In this case, probably some code that is shared between the aggregator and the downloader would need to be moved to a common package.
I was also wondering, whether this repo is moving to Go 1.21 at the future, since `slog` was introduced in to the standard lib in 1.21. So currently, this still relies on the `x/exp` package.
Fixesgocsaf#462
This PR adds structured logging for the aggregator service. Currently, only the text handler is used, but I can extend this to use the JSON handler as well. In this case, probably some code that is shared between the aggregator and the downloader would need to be moved to a common package.
I was also wondering, whether this repo is moving to Go 1.21 at the future, since `slog` was introduced in to the standard lib in 1.21. So currently, this still relies on the `x/exp` package.
Fixesgocsaf#462
The downloader now sports structure logging as its focus shifted towards an automation tool.
The aggregator always was thought as such a tool.
Therefore the aggregator should use the structured logging, too.
The text was updated successfully, but these errors were encountered: