mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Time-based monitoring #3188
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3188
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chengdada123 on GitHub (Mar 12, 2024).
📑 I have found these related issues/pull requests
no
🏷️ Feature Request Type
New monitor, Settings
🔖 Feature description
Hope it can be monitored over time. For example, I want to monitor the website from 20:00 at night to 8:00 in the morning. How can I achieve this? Thank you.
✔️ Solution
When adding monitoring, there is an option to monitor by time period.
❓ Alternatives
NO
📝 Additional Context
NO
@CommanderStorm commented on GitHub (Mar 12, 2024):
Currently, I would recommend enacting a scheduled maintenance when you don't want to get notified for downtimes. (=> 7:55-20:05)
In the future we plan to include more detailed scheduling, but this is tracked in numerous other issues. See https://github.com/louislam/uptime-kuma/pull/3447 and linked issues for our Plan.