aquasecurity/trivy

Configurable log format using trivy server

Open

#3,300 建立於 2022年12月14日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Go (35,000 star) (371 fork)batch import
help wantedkind/featurepriority/backlog

描述

We use trivy server to scan images from both CI pipelines and a Kubernetes operator. Our log infrastructure (Splunk) is much more fond of logs in machine-readable format (JSON), so it would be nice if it were possible to configure the log format when bootstrapping trivy server.

It seems like trivy uses https://github.com/uber-go/zap as the logging backend, supporting configuration, and JSON logging. A potential challenge could be that it seems hard to integrate Zap configuration with Viper/Cobra, ref. https://github.com/uber-go/zap/issues/542.

Related https://github.com/aquasecurity/trivy/issues/1526.

貢獻者指南

技術棧
go
領域
backendobservability
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingZap loggingViper configuration
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate how trivy initializes logging using zap and viper. Look at the related issue #1526 for previous discussion. Propose a method to add a log format flag that sets zap's logging format to JSON. Consider modifying the configuration struct and Cobra command to accept the flag and pass it to the logger initializer.
Configurable log format using trivy server · aquasecurity/trivy#3300 | Good First Issue