louislam/uptime-kuma

Graphing latency-results could be clearer

Open

#5524 opened on Jan 13, 2025

View on GitHub
 (10 comments) (2 reactions) (0 assignees)JavaScript (86,760 stars) (7,844 forks)batch import
A:dashboardA:monitorfeature-requesthelp wanted

Description

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

After little problematic update from uptime kuma 1 to current louislam/uptime-kuma:2.0.0-beta-slim.1 I have managed to get it running and now I am seeing some hard to understand graphs results and I am able to actually get what they mean.

  • some graphs (usually 1w) sometimes will not show dots of result (it is there just really not visible - if I hover with mouse around sometimes they appear) . Before all were visible always - I guess now they just disappear for main line. Screenshot 2025-01-12 at 15-48-32 Uptime Kuma_missing_green_points Screenshot 2025-01-13 at 06-27-41 Uptime Kuma_missing-points

  • some graphs shows two more lines up and down which are I am not able to decipher (i guess it is max/min but I am sometimes not sure how to interpret result - i have got it several times under 0 - as this is not possible it is confusing)? Screenshot 2025-01-13 at 06-26-56 Uptime Kuma_what_light_green_line_means

  • some graphs merge two other lines with previous and that makes it impossible to select dots with mouse as it jumps between them. Maybe two other lines should not show circles but directly dot on graph without being interactive? Screenshot 2025-01-13 at 12-20-05 Uptime Kuma_cannot_select_points_with_mouse

  • also several graphs now miss 0 on Y (response time) axis and we get some out scale? (This can be usually fixed with different duration). Then it is hard to compare. Screenshot 2025-01-13 at 06-26-41 Uptime Kuma_missing_0_axis_Y

📝 Error Message(s) or Log

There is no error in log (it is visual issue only i guess)

🐻 Uptime-Kuma Version

louislam/uptime-kuma:2.0.0-beta-slim.1

💻 Operating System and Arch

Kernel 5.13.0.x linux x86_64 nas

🌐 Browser

Mozilla Firefox 134.0 (but same thing happens in Chrome)

🖥️ Deployment Environment

  • Runtime: Docker 27.1.1
  • Database: sqlite
  • Filesystem used to store the database on: ext4
  • number of monitors: 28

Contributor guide

Tech stack
javascriptvuecss
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic Vue.js knowledgeFamiliarity with charting library (Chart.js)Ability to run uptime kuma locally
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Start by examining the chart rendering component, likely in `src/components/MonitorChart.vue` or similar. Look for Chart.js configuration for point display and Y axis min settings. Check recent commits that modified graph behavior (use `git log`). Reproduce the issues with different time ranges (1w, 1d) to understand the missing dots and overlapping lines. Investigate if the extra lines are due to min/max shading and consider adjusting interactive behavior.