← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 4545.h.2

日志作为事件流交给环境

理解等级:中级

短命实例的本地日志可能随实例消失,也难以跨节点聚合。服务把事件输出到标准输出等统一流,由执行环境决定路由、索引和保存,可把业务与日志设施分离。输出流本身不承诺耐久、完整或无背压,采集系统仍需定义丢失与保留策略。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • It’s All About Dependability · 查看原书依据

      a cloud native service should treat log information as nothing more than a stream of events, writing each event, unbuffered, directly to stdout. It shouldn’t concern itself with implementation trivialities like routing or storage of its log events, and allow the executor to decide what happens to them. Though seemingly simple (and perhaps somewhat counter-intuitive)

    参考来源

    - 位置:《Cloud Native Go》第06章《It’s All About Dependability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch06.xhtml) - 结论依据:短命实例的本地日志可能随实例消失,也难以跨节点聚合。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。 - 原始内容:a cloud native service should treat log information as nothing more than a stream of events, writing each event, unbuffered, directly to stdout. It shouldn’t concern itself with implementation trivialities like routing or storage of its log events, and allow the executor to decide what happens to them. Though seemingly simple (and perhaps somewhat counter-intuitive)