Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

RFC for pluggable logging model

未關閉
#161 13 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
powershell
領域
observability

研究方向

先閱讀 issue #106 以及此處引用的 PowerShell Committee 討論,以了解現有的 Splunk 特定語義。起草一份 RFC,定義彈性的 provider/plugin 模型,包括遠端和本機目標以及與 provider 無關的日誌記錄操作;當所提議的模型涵蓋這些情境並準備好接受社群回饋時,即視為完成。

由索引模型根據 Issue 內容生成。

描述

Per #106, this is to track the need for an RFC that would create a pluggable provider model for logging. Quoting me from that thread:

@PowerShell/powershell-committee discussed this one in detail today. We believe that there's massive value in figuring out how to tee logs off to remote logging providers, but a bunch of the semantics in this RFC are specific to Splunk.

Instead, we think an RFC should be authored that builds a provider/plugin model for allowing multiple remote logging providers. This RFC should also give consideration to whether local logging targets should be treated the same way (e.g. if you want to exclusively log to a remote target, maybe in serverless/stateless scenarios). There should also be a consideration of whether we should have something like a Get-PSLog or Write-PSLog that are agnostic to logging providers.

The PowerShell Team has a strong interest in picking this up, but we have no idea when we can get to it right now. We only know that it should be a flexible, pluggable model.

主要語言
PowerShell
星號
468
分支
143
平均合併
9 小時 5 分鐘
30 天內合併 PR
1

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

PowerShell/PowerShell-RFC 的其他 Issue

查看 PowerShell/PowerShell-RFC 的全部 Issue

相似的 Issue

更多 Observability & SRE Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。