[HardMax71]

Summary

Small bug found while checking release 2026.10.34 (#452) on prod. The collector's first write created logs-2026.10.22 at 19:57:10.224, 0.3 s before start.sh put the index template in (OpenSearch logged "templates []"). That index got default mappings: attributes and resource as plain objects, so mixed key types can reject lines, plus one replica that keeps it yellow on a single node.

Changes

Compose starts OpenSearch with action.auto_create_index=-logs-*,+*, so a write can't create a logs- index yet; it gets index_not_found_exception and is dropped, and Loki has the line. start.sh allows auto-creation with a persistent cluster setting once the template and the retention policy exist, so every logs- index gets both when it's created, and the step that attached the policy afterwards is gone. A restart reads the setting from the data volume.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• CI/CD or tooling changes

Test Plan

• Backend unit tests pass (cd backend && uv run pytest tests/unit)
• Frontend unit tests pass (cd frontend && npm run test)
• Backend E2E tests pass (docker compose exec -T backend sh -c 'uv sync --group test --no-dev --frozen --no-install-project --no-build && pytest tests/e2e')
• Frontend E2E tests pass (cd frontend && npm run test:e2e)
• API spec and client regenerated if routes or schemas changed (./deploy.sh openapi, then ./deploy.sh types), never edited by hand
• Manual testing performed

Validation: fresh OpenSearch 3.9 from this branch with a loop writing to today's index every 200 ms. Writes before setup got index_not_found_exception, the index was then created with templates [logs], flat_object mappings, 0 replicas and the logs-30d policy. After a restart a write created tomorrow's index the same way.

Checklist

• My code follows the project's style guidelines
• I have run pre-commit run --all-files and all checks pass
• I have added tests that prove my fix/feature works
• I have updated documentation if needed
• My changes don't introduce new warnings

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8f747b43-e1d1-4ffe-a504-f2c88675a3f8

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Flag	Coverage Δ
backend-e2e	82.04% <ø> (ø)
backend-unit	77.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Backend	94.73% <ø> (ø)
Frontend	92.25% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.