如何解决我如何处理元素的日志记录集合
我正在将日志发布到 ELK 堆栈,但我无法决定应该如何处理日志记录集合。
我正在这些日志记录变体之间进行选择:
a)
INFO (scope/properties/context like UserId,SubscriptionType etc)... Publishing order {OrderId} of type {OrderType} ...
INFO (scope/properties/context like UserId,SubscriptionType etc)... Publishing order {OrderId} of type {OrderType} ...
___
INFO (scope/properties/context like UserId,SubscriptionType etc)... Successfully published order {OrderId} in cart {CartId} ...
INFO (scope/properties/context like UserId,SubscriptionType etc)... Failed publishing order {OrderId} ...
INFO (scope/properties/context like UserId,SubscriptionType etc)... Successfully published order {OrderId} in cart {CartId} ...
b)
INFO (scope/properties/context like UserId,SubscriptionType etc)... Publishing orders {CollectionOfObjectsWithOrderInfo} ...
___
INFO (scope/properties/context like UserId,SubscriptionType etc)... Successfully placed orders {CollectionOfObjectsWithOrderInfo} ...
INFO (scope/properties/context like UserId,SubscriptionType etc)... Failed placing orders {CollectionOfObjectsWithOrderInfo} ...
我正在考虑的要点:
- 处理日志的困难
- 日志大小
- 日志产生的流量
关于第一点,我认为使用日志会更容易,因为过滤和搜索会更灵活。
但我非常担心考虑到第 2 点和第 3 点可能出现的问题。
您将如何处理这种情况?
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。