Backlog/v12 datasources log timeline

[AlexSanchez-bit]

No description provided.

[github-actions]

🛑 AI review — High/critical findings

One or more high/critical issues were found. Please review and fix before merging if they're real.

⚠️ architecture (gemini-3-flash-lite) — minor findings

Summary: Update AWS SDK dependencies, add time range filtering to datasources ingestion timeline, and adjust time window resolution.

• low backend/modules/eventprocessing/usecase/ingestion_stats.go:133 — The time window resolution logic now assigns raw strings like 'now' or 'now-' directly. Ensure that downstream parsers or queries correctly support relative time expressions to prevent query execution errors.

🛑 bugs (gemini-3-flash-lite) — high/critical — please review

Summary: Broken Go implementation in resolveWindow using invalid time query strings

• high backend/modules/eventprocessing/usecase/ingestion_stats.go:134 — resolveWindow replaces proper UTC parsing with raw string literals like "now" and "now-24h0m0s", which will not be parsed correctly as timestamps by underlying database or date-histogram queries, breaking the ingestion timeline API.

✅ security (gemini-3-flash-lite) — clean

Summary: Routine dependency version bumps and addition of time range filtering for ingestion stats.

No findings.

🟢 go-deps — up to date

No pending Go dependency updates.

[AlexSanchez-bit]

semantic time ranges are supported by opensearch, time window processor was limiting those time ranges