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.