Add JSON logging format support for scan jobs and enforcer

[moshemorad]

Summary

Add opt-in JSON log output (one object per line) so KRR logs are easier to index, search, and filter with log scrapers such as Filebeat. This aligns KRR with the logging approach used across the other Robusta services (runner, Holmes, relay), all driven by the same ENABLE_JSON_LOGS_FORMAT toggle. Part of ROB-459.

Key Changes

• Scanner (robusta_krr/core/models/config.py): set_config() emits a python-json-logger JsonFormatter (with levelname → severity) when ENABLE_JSON_LOGS_FORMAT is set. This is read from the environment only — never a CLI flag — so the interactive CLI keeps its Rich output. The runner sets this env var on the KRR scan Job (only when KRR_PUSH_SCAN is enabled, since the non-push path parses the result out of the job's combined stdout/stderr logs).
• Enforcer (enforcer/enforcer_main.py): the resident enforcer pod swaps its plain formatter for the same JSON formatter when the toggle is set.
• Helm (helm/krr-enforcer): new enableJsonLogsFormat value (with global.enableJsonLogsFormat honored as a fallback) wired to the ENABLE_JSON_LOGS_FORMAT container env var.
• Dependencies: add python-json-logger; poetry.lock regenerated with Poetry 1.8.5 (matching the committed lock's generator) so the change is limited to adding the new package.

Notes

• Default behavior is unchanged: with the toggle off, the scanner keeps Rich output and the enforcer keeps its plain text format.
• The interactive CLI is intentionally never switched to JSON.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AozEpN8uwPRQuF8FPRX4Jy

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0a683bf2-9ca4-4aea-aef3-9e5653bdf0bb

📥 Commits

Reviewing files that changed from the base of the PR and between 2657080 and cefb2b2.

📒 Files selected for processing (2)

• enforcer/enforcer_main.py
• robusta_krr/core/models/config.py

🚧 Files skipped from review as they are similar to previous changes (2)

• enforcer/enforcer_main.py
• robusta_krr/core/models/config.py

---

Walkthrough

Adds optional JSON log formatting controlled by ENABLE_JSON_LOGS_FORMAT, updates both Python logging paths, adds the JSON logger dependency, and wires the setting through Helm values into the enforcer Deployment.

Changes

JSON logging configuration

Layer / File(s)	Summary
Runtime JSON logging setup pyproject.toml, requirements.txt, enforcer/requirements.txt, robusta_krr/core/models/config.py, enforcer/enforcer_main.py	Adds python-json-logger and selects JSON or existing plain-text formatting based on the environment variable, including the severity field mapping.
Helm logging value wiring helm/krr-enforcer/values.yaml, helm/krr-enforcer/templates/enforcer.yaml	Adds the logging toggle and injects ENABLE_JSON_LOGS_FORMAT into the Deployment using global, local, and default values.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding JSON logging support for scan jobs and the enforcer.
Description check	✅ Passed	The description is directly related to the changes and accurately summarizes the JSON logging work.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/json-log-format-runner-vqbzst

---

_{Comment @coderabbitai help to get the list of available commands.}