mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Upside down mode does not log response time in chart #4244
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#4244
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 @victorwon on GitHub (Aug 5, 2025).
Originally assigned to: @ashhley04 on GitHub.
📑 I have found these related issues/pull requests
Can't find related reports.
🛡️ Security Policy
📝 Description
I created a upside-down mode monitor for 3xx redirects, meaning it fails if url is being redirected. It works fine except the response chart is always blank. Anyone know how to work around or fix it? Tried both on stable and beta versions, same issue.
Btw, if uncheck the upside-down switch then the response charts show properly.
Thanks.
👟 Reproduction steps
👀 Expected behavior
The chart should always show response time no matter upside-down mode.
😓 Actual Behavior
Chart only works as expected when upside-down mode is off.
🐻 Uptime-Kuma Version
dockerhub image louislam/uptime-kuma:beta and louislam/uptime-kuma:1
💻 Operating System and Arch
docker
🌐 Browser
Chrome
🖥️ Deployment Environment
cat docker-compose.yml
version: "3"
services:
kuma:
container_name: kuma
image: louislam/uptime-kuma:beta
volumes:
- uptime-kuma:/app/data
restart: unless-stopped
ports:
- "3001:3001"
network_mode: bridge
volumes:
uptime-kuma:
📝 Relevant log output
@ashhley04 commented on GitHub (Oct 8, 2025):
can i work on this ?
@CommanderStorm commented on GitHub (Oct 8, 2025):
Sure.
Make sure to reproduce the issue first and then look at the things coming via the network if this is a backend/frontend issue
@AlishaaCrasto commented on GitHub (Oct 9, 2025):
can i work on this ?
@CommanderStorm commented on GitHub (Oct 9, 2025):
Let's not waste @ashhley04 's time by having two people working on this issue ^^
@louislam commented on GitHub (Oct 9, 2025):
@CommanderStorm I think they look suspicious, they sent the same comments
can i work on this ?(there is a space character before the question mark) among the repo with different usernames.I have looked into a commit, it is literally vibe code.
github.com/Angel-Mathew007/uptime-kuma@8fa1187e0e@ashhley04 commented on GitHub (Oct 10, 2025):
@louislam @CommanderStorm
We’ve been given a task from our university to contribute to open-source projects by solving around 4–5 issues in existing repositories.
Please note that this is not spam — our comments and pull requests are part of our academic project. We’ll make sure our contributions are meaningful and relevant to your repository.
These are my team members
@AlishaaCrasto
@ashhley04
@Angel-Mathew007
@burbozaastha
Thank you for your understanding! 🙏
@louislam commented on GitHub (Oct 10, 2025):
@ashhley04 From what I saw, @Angel-Mathew007's commits were randomly changing files for no reason, you guys should be using GitHub Copilot agent mode or something.
If you really want to contribute, please turn off agent mode, understand the issue, understand the codebase and do it by yourself.
If your academic project is asking you to use AI to contribute, you may have to find another open source project.
AI generated code is not allowed here.
Thank you for your understanding too.