Make alert cooldown configurable and increase default to 15 minutes

[fakebizprez]

Motivation

• Reduce frequency of repeated Slack alerts by increasing the default cooldown between identical alerts.
• Allow operators to tune the cooldown without code changes by exposing an environment variable.

Description

• Added an optional alert_cooldown parameter to WebhookService.__init__ and increased the default cooldown from 300s to 900s (15 minutes) when not provided.
• Wired a new ALERT_COOLDOWN_SECONDS environment variable into startup in temp_monitor.py and pass it to WebhookService via the alert_cooldown argument.
• Documented the new ALERT_COOLDOWN_SECONDS variable in .env.example and README.md and updated the defaults accordingly.

Testing

• No automated tests were executed as part of this change; existing unit tests that exercise cooldown logic live in test_webhook.py and can be run with python test_webhook.py to validate behavior.

---

Codex Task

Summary by CodeRabbit

Release Notes

• New Features

  • Added configurable alert cooldown period via the ALERT_COOLDOWN_SECONDS environment variable, allowing customization of the minimum time between repeated identical alerts.

• Documentation

  • Updated configuration documentation to include the new alert cooldown setting.

• Changes

  • Default cooldown period between identical alerts increased from 5 minutes to 15 minutes.

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

[greptile-apps]

Skipped: This PR does not contain any of your configured labels: (greptile)

[coderabbitai]

Walkthrough

The PR introduces a configurable alert cooldown mechanism by adding an ALERT_COOLDOWN_SECONDS environment variable (default 900 seconds) that controls the frequency of repeated alert types. This value flows from environment configuration through the application initialization to the WebhookService, replacing the previously hard-coded 300-second cooldown.

Changes

Cohort / File(s)	Summary
Configuration & Documentation ​.env.example, README.md	Added ALERT_COOLDOWN_SECONDS environment variable with default value 900 and corresponding documentation entry under Alert Thresholds section
Service Initialization temp_monitor.py	Modified to read ALERT_COOLDOWN_SECONDS from environment and pass it as alert_cooldown parameter to WebhookService constructor
Core Service Logic webhook_service.py	Updated WebhookService.__init__ to accept optional alert_cooldown parameter (default 900 seconds) and use it for controlling repeated alert frequency instead of hard-coded 300-second value

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Alert cooldowns, oh what a delight,
Fifteen minutes between messages tonight,
No more spam floods from the same old cry,
The webhook hops freely, way up high! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately captures the main changes: making alert cooldown configurable and increasing the default from 300s to 900s (15 minutes).

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@README.md`:
- Line 105: Update the README text that still says "5-minute cooldown between
same alert type" to reflect the actual default of 15 minutes (900 seconds) or
make it reference the ALERT_COOLDOWN_SECONDS variable; locate the sentence in
the README that mentions the 5-minute cooldown and change it to either
"15-minute cooldown (ALERT_COOLDOWN_SECONDS = 900 seconds)" or a phrasing that
points readers to the ALERT_COOLDOWN_SECONDS configuration value so the docs
match the code.

🧹 Nitpick comments (1)

temp_monitor.py (1)

559-560: Consider passing alert_cooldown when dynamically creating WebhookService.

When a WebhookService is created dynamically via the PUT /api/webhook/config endpoint (line 560), the alert_cooldown parameter is not passed, so it defaults to 900 seconds. This differs from the initial service creation (lines 126-130) which respects ALERT_COOLDOWN_SECONDS.

If the intent is for all webhook services to honor the environment variable, consider storing alert_cooldown_seconds at module level and passing it here as well.

Suggested approach

 # Initialize webhook service
 webhook_service = None
+alert_cooldown_seconds = int(os.getenv('ALERT_COOLDOWN_SECONDS', '900'))
 slack_webhook_url = os.getenv('SLACK_WEBHOOK_URL')
 if slack_webhook_url:
     webhook_config = WebhookConfig(
         ...
     )
-    alert_cooldown_seconds = int(os.getenv('ALERT_COOLDOWN_SECONDS', '900'))
     ...

Then at line 560:

                 if not webhook_service:
-                    webhook_service = WebhookService()
+                    webhook_service = WebhookService(alert_cooldown=alert_cooldown_seconds)

And similarly at line 583.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Documentation inconsistency with existing text.

Line 198 still states "5-minute cooldown between same alert type" but the new default is 15 minutes (900 seconds). Consider updating line 198 to reflect the new configurable default or reference the ALERT_COOLDOWN_SECONDS variable.

Suggested fix for line 198

-- **Alert Cooldown**: 5-minute cooldown between same alert type (prevents spam)
+- **Alert Cooldown**: Configurable cooldown between same alert type (default: 15 minutes, see `ALERT_COOLDOWN_SECONDS`)

🤖 Prompt for AI Agents

In `@README.md` at line 105, Update the README text that still says "5-minute
cooldown between same alert type" to reflect the actual default of 15 minutes
(900 seconds) or make it reference the ALERT_COOLDOWN_SECONDS variable; locate
the sentence in the README that mentions the 5-minute cooldown and change it to
either "15-minute cooldown (ALERT_COOLDOWN_SECONDS = 900 seconds)" or a phrasing
that points readers to the ALERT_COOLDOWN_SECONDS configuration value so the
docs match the code.