feat: set data retention in OpenObserve to 30 days

[nilushancosta]

Purpose

The default data retention time in OpenObserve is 10 years. This PR updates it to 30 days in OpenChoreo modules

Approach

Passed config.ZO_COMPACT_DATA_RETENTION_DAYS: "30" to the upstream Helm chart values files

Related Issues

openchoreo/openchoreo#4257

Checklist

• Tests added or updated (unit, integration, etc.)
• Samples updated (if applicable)

Remarks

Add any additional context, known issues, or TODOs related to this PR.

Summary by CodeRabbit

• New Features
  • Configured OpenObserve to retain compacted data for 30 days across standalone and standard deployment configurations.
  • Applied the same retention setting to both logging and tracing observability deployments.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 05cddef4-908c-4950-919d-cb3e33dbe9a8

📥 Commits

Reviewing files that changed from the base of the PR and between f031f94 and 9e2c42f.

📒 Files selected for processing (2)

• observability-logs-openobserve/helm/values.yaml
• observability-tracing-openobserve/helm/values.yaml

---

📝 Walkthrough

Walkthrough

Both OpenObserve Helm values files now set compact data retention to 30 days for standalone and disabled OpenObserve configurations.

Changes

OpenObserve retention configuration

Layer / File(s)	Summary
Configure 30-day retention observability-logs-openobserve/helm/values.yaml, observability-tracing-openobserve/helm/values.yaml	Adds ZO_COMPACT_DATA_RETENTION_DAYS: "30" under the standalone and OpenObserve configuration blocks. The OpenObserve blocks remain disabled where previously specified.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related issues

• openchoreo/openchoreo#4257 — Sets OpenObserve data retention to 30 days in both observability modules.

Suggested reviewers: akila-i

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: setting OpenObserve data retention to 30 days.
Description check	✅ Passed	The description follows the template and fills Purpose, Approach, Related Issues, Checklist, and Remarks.
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 unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.3.8)

observability-logs-openobserve/helm/values.yaml

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

observability-tracing-openobserve/helm/values.yaml

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

---

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.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[akila-i]

is there a way to set different retention periods to different streams? (eg: container logs and k8s events)

[nilushancosta]

This is not supported through the Helm chart. Let me see if there is a way to do it using an API call