Establish a standard logging format through this library, with the ability to customize
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 12/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- python
调研方向
The payload names the existing dockerflow.logging.MozlogHandler and a proposed generic dockerflow.logging.DefaultHandler, selected by a DOCKERFLOW_LOGGING_FORMAT environment variable. The first step is to read the current logging handlers in the package and see how the Mozlog format is built. The issue leaves the class name ('real name tbd') and the supported format values open, so a contributor would first need a maintainer decision on the design before any code change.
由索引模型根据 Issue 内容生成。
描述
Though we want to add the ability to emit logs in the format that's most useful for engineers (see #111), we also want to promote a standard logging format to reduce the cognitive overhead of switching between projects and provide the ability to more-easily search for logs that span multiple services.
The idea would be that instead of encouraging engineers to reference a format-specific class in their logging configuration (e.g. dockerflow.logging.MozlogHandler or google.cloud.logging.handlers.StructuredLogHandler), we can establish a generic class name like:
'console': {
'class': 'dockerflow.logging.DefaultHandler', #real name tbd
},
with some sort of ability to configure the class through an environment variable, like:
os.getenv("DOCKERFLOW_LOGGING_FORMAT", "MOZLOG")
With this setup, engineers have the freedom to:
- accept the default format of
DefaultHandleras the "current logging format standard of Mozilla".- maintainers of this library can change the format of
DefaultHandlerin accordance with the current logging standard of Mozilla, and if engineers only care about aligning with Mozilla's standard logging format, they'll automatically be compliant with the standard when they update this library
- maintainers of this library can change the format of
- override the standard format to another commonly used format through environment configuration, like
export DOCKERFLOW_LOGGING_FORMAT=GCP
- still (of course) have the ability to fully customize their logging setup by referencing specific logging handlers, formatters, and filters
- 主要语言
- Python
- 星标
- 41
- 派生
- 21
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
mozilla-services/python-dockerflow 的其他 Issue
-
难度 3/5 半天 新手友好度 15/100
mozilla-services/python-dockerflow#119 · 1 条评论 ·
-
难度 2/5 1 小时以内 新手友好度 15/100
mozilla-services/python-dockerflow#117 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 15/100
mozilla-services/python-dockerflow#116 · 1 条评论 ·
-
难度 3/5 半天 新手友好度 62/100
-
难度 3/5 1-2 天 新手友好度 35/100
查看 mozilla-services/python-dockerflow 的全部 Issue
相似的 Issue
-
tunneld on Windows: Wi-Fi devices are not discovered because uvicorn runs on a ProactorEventLoop未关闭
难度 2/5 1-3 小时 新手友好度 76/100
doronz88/pymobiledevice3#2051 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
collabnix/awesome-mcp-lists#230 ·
维护者通常 9 天内回复
-
Groc schedules with out of range values pass config validation and fail later when the scheduler is built可能已有人在做 @auraseb 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
autowarefoundation/autoware_carla_scenario#342 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 72/100
ianktoo/project-monitor#14 ·