Fix default log level

[Tzvonimir]

Summary by CodeRabbit

• Chores
  • Updated default logging level configuration from "warn" to "error" for the zxporter service. Users deploying with default settings will now see only error-level logs.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The zxporter Helm chart's default logging level is updated from "warn" to "error" in the values configuration file, increasing the minimum severity threshold for logged messages.

Changes

Cohort / File(s)	Summary
zxporter Helm configuration helm-chart/zxporter/values.yaml	Changed default logLevel from "warn" to "error"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update log levels #215: Introduced the logLevel key in the zxporter Helm values template; this PR modifies its default value from "warn" to "error".

Suggested reviewers

• Parthiba-Hazra

Poem

🐰 Logs now whisper only when errors appear,
"Warn" steps aside, "error" takes the sphere,
Quieter deployments, cleaner the air,
One little change, with logging care! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Fix default log level' directly and clearly summarizes the main change: updating the default log level in the Helm chart values from 'warn' to 'error'.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch tzvonimir/fix-default-log-level

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61a7680 and 7ce5225.

📒 Files selected for processing (1)

• helm-chart/zxporter/values.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Build Docker Image
• GitHub Check: Build Docker Image
• GitHub Check: Run make test
• GitHub Check: Analyze (go)

🔇 Additional comments (1)

helm-chart/zxporter/values.yaml (1)

53-55: Verify the log level comment reflects all supported values and confirm the rationale for changing from the previous default.

The comment on line 53 lists valid values as "debug, info, error", but according to the AI summary, the previous default was "warn". Please:

1. Confirm whether "warn" is actually supported by zxporter's logging implementation
2. If "warn" is not valid, update the comment to reflect that this change fixes an invalid configuration
3. Document whether changing to "error" as the default is intentional for production deployments, as this suppresses warning-level visibility

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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