fix(collector-health): use a journalctl-parseable delay-gate window

[proerror77]

Summary

• DELAY_GATE_WINDOW=15min is not a valid journalctl --since timestamp. Verified on the target host (monday-trade-data-26): journalctl --since 15min fails with Failed to parse timestamp: 15min, so after the feat(collector): add durable collector-host health monitoring #735 install both LOB units report a permanent journald query failed (exit 1) breach — two false-positive breaches in every health snapshot.
• Fix: DELAY_GATE_WINDOW='15 min ago', verified parseable by journalctl on the target host.
• The mock-journalctl test harness never exercised real timestamp parsing, which is why feat(collector): add durable collector-host health monitoring #735 CI was green.

Issue relationship

None

Validation

• bash -n clean, git diff --check clean
• deployment/aliyun/test-monday-collector-health.sh: 53 passed, 0 failed
• Host readback of the failure mode and the parseable replacement (Aliyun Cloud Assistant invocation t-jpn6t9v4p1irh8g)
• .github/scripts/agent-worktree-preflight.sh check exits 141 on this machine (SIGPIPE from its own git worktree list | awk under pipefail with ~130 registered worktrees — pre-existing script issue, unrelated to this change); ownership record verified manually against the same checks.

One-line fix; redeploy of the installed script to the host follows after merge.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@proerror77, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5b995534-d09a-4ccf-9bb3-13e8bf250e55

📥 Commits

Reviewing files that changed from the base of the PR and between 1b701e4 and a30f434.

📒 Files selected for processing (1)

• deployment/aliyun/monday-collector-health.sh

---

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