a8m / a8m/kinesis-producer

Logrus Entry vs Logger

未关闭
#23 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Go
星标
150
派生
47
PR 合并指标
30 天内没有已合并 PR

描述

To support logging already defined fields using logrus, is there any concern with switching to `Entry` rather than `Logger`?

From [logrus docs](https://github.com/sirupsen/logrus/blob/master/entry.go#L47):

```
These objects can be reused and passed around as much as you wish to avoid field duplication.
```

Add [README](https://github.com/sirupsen/logrus#default-fields)

```
Often it's helpful to have fields always attached to log statements in an application or parts of one. For example, you may want to always log the request_id and user_ip in the context of a request. Instead of writing log.WithFields(log.Fields{"request_id": request_id, "user_ip": user_ip}) on every line, you can create a logrus.Entry to pass around instead:
```

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。