-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.json
1 lines (1 loc) · 10 KB
/
index.json
1
[{"categories":null,"content":"Golang在工程实践中的错误处理 -- 石墨文档产研负责人[彭友顺]","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"\r来源\r本文来自于: Golang在工程实践中的错误处理 – 石墨文档产研负责人[彭友顺] 我仅用来学习, PPT是群里一个群友发的 ","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:0:0","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"错误处理为什么慢\r错误信息不够完善 错误处理不够优雅 分布式错误难以串联 错误信息难以识别 ","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:1:0","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"如何完善错误信息\r","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:2:0","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"为何调试慢 – 错误信息少\r错误信息少, 每遇到一个问题, 就追加一个日志字段, 排查错误效率非常低 以一个grpc错误日志param error为例, 不知道哪个client, 哪一行代码, 哪一方的参数问题 {\"lv\": \"error\", \"ts\": 1711111870, \"msg\": \"grpc error\", \"error\": \"param error\"}","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:2:1","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"如何解决\r完善错误信息 对端信息: 能够确定对端的唯一来源, 例如应用名称, 对端的配置, 对端的ip等 请求方法: 对端请求的方法 请求参数: 请求的参数信息, 包括header里的metadata 响应数据: 响应的数据, 包括header里的metadata 状态信息: 错误码和错误信息 耗时时间: 请求到响应的耗时时间 执行行号: 调用处执行的行号 高亮信息 调试阶段, 日志用红色高亮错误 肉眼才能组快的定位到error日志 利用现代IDE, 直接点开代码执行行号, 跳转到指定的代码位置 组件封装 框架错误处理信息 脏活累活交给框架 组件要全面统一 ","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:2:2","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"优雅处理错误信息\r记录一次错误 对于一个同样的错误, 杂音非常多 每个err, 都去查看一次对应代码, 效率非常低 过多记录会占用存储空间 应该在最外层入口处只记录一次错误空间 不要透传错误 使用fmt.Errorf() 如果不考虑性能 日志开启stack 错误追加stack 错误码唯一性 对于一个错误, 可能有多个原因, 仍需查看代码以确定具体情况 错误码唯一性, 准确地反映出错误的根本原因, 才能快速定位问题 如果不在写代码的时候花时间做唯一错误码, 那么只能在排查的时候花更多时间查问题 ","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:3:0","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"分布式错误处理\r分布式信息 调用链复杂, 服务A的问题, 可能是其他B,C等服务引起的 错误尽早失败 核心错误, 应该直接让系统panic 必要的错误信息, 判断在哪个地方报错, 哪个微服务有问题 错误信息高亮, 显示红色让错误更明显 核心错误中断系统启动, 让错误显示在最后一行 不让报错传递到别的服务 使用TraceId串联服务 ","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:4:0","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"为什么恢复慢\r经验: 为什么年纪大的程序员会比年轻程序员排查问题更快 遇到的问题多 这些问题不会系统的出现在课本上 没遇到过的问题, 很难意识到对应的操作手段 识别 将认知总结为文档 故障演练 自动化 自己写文档, 代码和文档不一致 有错误码找不到代码对应地方 有错误不知道是哪个版本的代码 错误码在代码中还有没有使用, 错误码越变越多 错误码孵化, 没用的错误码应该随版本下线 错误码的SOP, 国际化问题 ","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:5:0","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"相关链接\rhttps://github.com/gotomicro/ego https://github.com/ego-component https://mp.weixin.qq.com/s/xXGjlSYOmY_uz6ZsbLSIEw https://github.com/clickvisual/clickvisual ","date":"2024-06-18","objectID":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/:6:0","tags":null,"title":"Golang在工程实践中的错误处理","uri":"/golang%E5%9C%A8%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5%E4%B8%AD%E7%9A%84%E9%94%99%E8%AF%AF%E5%A4%84%E7%90%86/"},{"categories":null,"content":"Windows10 Vmware17 安装Centos-9-stream 引导界面卡顿.","date":"2024-06-16","objectID":"/windows10-vmware17-%E5%AE%89%E8%A3%85centos-9-stream-%E5%BC%95%E5%AF%BC%E7%95%8C%E9%9D%A2%E5%8D%A1%E9%A1%BF/","tags":null,"title":"Windows10 Vmware17 安装Centos-9-stream 引导界面卡顿","uri":"/windows10-vmware17-%E5%AE%89%E8%A3%85centos-9-stream-%E5%BC%95%E5%AF%BC%E7%95%8C%E9%9D%A2%E5%8D%A1%E9%A1%BF/"},{"categories":null,"content":"\r环境\r环境: Windows10, vmware17, Centos-9-Stream-latest, AMD-7900x 在引导界面非常卡, 页面无法正确显示, 点击无反应/响应慢 解决办法\r解决办法: 在配置虚拟机时, 内存和CPU多分配一点 一开始分配的是16G和6(32)核, 上网检索发现了一篇类似的帖子, 然后分配了32G+12(62)核, 成功安装! ","date":"2024-06-16","objectID":"/windows10-vmware17-%E5%AE%89%E8%A3%85centos-9-stream-%E5%BC%95%E5%AF%BC%E7%95%8C%E9%9D%A2%E5%8D%A1%E9%A1%BF/:0:0","tags":null,"title":"Windows10 Vmware17 安装Centos-9-stream 引导界面卡顿","uri":"/windows10-vmware17-%E5%AE%89%E8%A3%85centos-9-stream-%E5%BC%95%E5%AF%BC%E7%95%8C%E9%9D%A2%E5%8D%A1%E9%A1%BF/"},{"categories":null,"content":"XiaoLiang's friends","date":"2024-06-05","objectID":"/friends/","tags":null,"title":"","uri":"/friends/"},{"categories":null,"content":"Base info\r# 朋友/站点信息例子 - nickname: 朋友名字 avatar: 朋友头像 url: 站点链接 description: 对朋友或其站点的说明","date":"2024-06-05","objectID":"/friends/:1:0","tags":null,"title":"","uri":"/friends/"},{"categories":["cncf"],"content":"在国内搭建起k8s集群属实不易, 全是泪","date":"2024-03-13","objectID":"/k8s-v1.29%E9%9B%86%E7%BE%A4%E6%90%AD%E5%BB%BA-%E9%81%BF%E5%9D%91%E6%8C%87%E5%8D%97/","tags":null,"title":"K8s V1.29集群搭建-避坑指南","uri":"/k8s-v1.29%E9%9B%86%E7%BE%A4%E6%90%AD%E5%BB%BA-%E9%81%BF%E5%9D%91%E6%8C%87%E5%8D%97/"},{"categories":["cncf"],"content":"k8s集群搭建-v1.29.0\rk8s-version: v1.29.0 os-release: centos7 ","date":"2024-03-13","objectID":"/k8s-v1.29%E9%9B%86%E7%BE%A4%E6%90%AD%E5%BB%BA-%E9%81%BF%E5%9D%91%E6%8C%87%E5%8D%97/:0:0","tags":null,"title":"K8s V1.29集群搭建-避坑指南","uri":"/k8s-v1.29%E9%9B%86%E7%BE%A4%E6%90%AD%E5%BB%BA-%E9%81%BF%E5%9D%91%E6%8C%87%E5%8D%97/"},{"categories":null,"content":"关于我\r","date":"2024-01-31","objectID":"/about/:0:0","tags":null,"title":"About","uri":"/about/"},{"categories":null,"content":"简单介绍\r年龄:00年 家乡:河北邯郸 学校:河北大学 技术:菜鸡程序员 现状:坚持努力提升技术中 ","date":"2024-01-31","objectID":"/about/:1:0","tags":null,"title":"About","uri":"/about/"},{"categories":null,"content":"联系我\rQQ: 762610973 WeChat:xl762610973 Email:jxl762610973@gmail.com ","date":"2024-01-31","objectID":"/about/:2:0","tags":null,"title":"About","uri":"/about/"},{"categories":null,"content":"Build My Blog Site\ruse hugo and fixit Engine: Hugo Theme: FixIt ","date":"2024-01-31","objectID":"/buildsite/:0:0","tags":null,"title":"BuildSite","uri":"/buildsite/"},{"categories":null,"content":"Record\r实用工具 工作和学习 生活 ","date":"2024-01-31","objectID":"/buildsite/:1:0","tags":null,"title":"BuildSite","uri":"/buildsite/"},{"categories":null,"content":"End\rpackage main func main() { println(\"hello, world\") }fn main() { println!(\"hello, world\") }","date":"2024-01-31","objectID":"/buildsite/:2:0","tags":null,"title":"BuildSite","uri":"/buildsite/"}]