mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Solução para a de Status #2507
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#2507
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 @gildasio719 on GitHub (Aug 21, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
In projects involving hundreds of monitors, it's crucial to recognize that monitoring efficiency is greatly enhanced by focusing solely on assets that have experienced downtime. Therefore, the optimal approach would be to place status 0, or rather the 'down' status, at the top of the status page.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.0
💻 Operating System and Arch
Windows, linux
🌐 Browser
Google Chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response
@CommanderStorm commented on GitHub (Aug 21, 2023):
No, this is currently not a feature.
I don't see the question in this issue. Did you mean to open a
feature-requestfor this?If yes, please close this issue (editing tags is something only Louis can do) and include:
See https://github.com/louislam/uptime-kuma/issues/1585 and the PR implementing this feature https://github.com/louislam/uptime-kuma/pull/3312
⇒ how do you think this feature should work?
@chakflying commented on GitHub (Aug 22, 2023):
Duplicate of #1936
@CommanderStorm commented on GitHub (Aug 22, 2023):
@gildasio719
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
@gildasio719 commented on GitHub (Aug 22, 2023):
Ok Thanks