mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
More detailed title display on the status page? #4594
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#4594
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 @luyii-code-1 on GitHub (Jan 9, 2026).
📑 I have found these related issues/pull requests
Currently, on the status page, Kuma only shows 'Online', 'Partially Offline', and the like.
🔖 Feature description
Is it possible to add a JavaScript check to the title so that it changes according to the status? For example, when a critical service is offline, an edge service is offline, there is a routing error, and more, the status page could be turned into a page where the status is clear at a glance.
✔️ Solution
add a JavaScript check that read the status of monitors
❓ Alternatives
I consident to write it by myself,but unluckily,UptimeKuma developed on a language that I non't learned
📝 Additional Context
I use it on my school's services ,and it is import to have a page toknow global status and directly know the bad things
@CommanderStorm commented on GitHub (Jan 9, 2026):
I think this would need a bit deeper thinking and is likely better by allowing on the status page settings tick a checkbox to mark this as a critical service.
I don't think adding allowing users to customise too much about this is worth it, not many will do this.
On the status page settings, hidden away, that is fine though.
@luyii-code-1 commented on GitHub (Jan 9, 2026):
Indeed, setting up critical services is useful. When I used monitoring for grading papers at school last month, I employed grouping to label two external HTTP pages as “critical services that determine user access.” With this feature in place, users can immediately see whether they can access the page or not.
---Original---
From: "Frank @.>
Date: Sat, Jan 10, 2026 09:44 AM
To: @.>;
Cc: @.@.>;
Subject: Re: [louislam/uptime-kuma] More detailed title display on the status page? (Issue #6663)
CommanderStorm left a comment (louislam/uptime-kuma#6663)
I think this would need a bit deeper thinking and is likely better by allowing on the status page settings tick a checkbox to mark this as a critical service.
I don't think adding allowing users to customise too much about this is worth it, not many will do this.
On the status page settings, hidden away, that is fine though.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>