Seems like Uptime details page shows % instead of actual values

[dmythro]

Uptime list shows actual response times in the chart. But details page shows values 0-100.

Expected behavior

If page response is 321ms I expect to see these actual values in details page.

Screenshots

this website in the list:

this website in details (same for Uptime):

Additional context

API has responseTime and originalResponseTime, and there originalResponseTime is a correct value and responseTime seem like a percentage (0-100).

[AlizaRK]

Hi, can I take this issue?

[ajhollid]

Looks to me that those are the normalized values that are displaying in the tool tip.

All response times are normalized between 0 and 100 for display purposes.

This should be a simple fix as the original response time is also included in the api response.

[dmythro]

Seems like infrastructure charts don't even have tooltips — would be cool to fix that too, so we could see the actual values at some point in time as well, like it works in uptime.

[ajhollid]

Seems like infrastructure charts don't even have tooltips — would be cool to fix that too, so we could see the actual values at some point in time as well, like it works in uptime.

Good idea, should be relatively straight forward

[AlizaRK]

Hi, even though I haven’t been assigned this issue, I went ahead and created the fixes and changes based on this conversation to get familiar with the Checkmate codebase (I am new here). Please have a look and let me know if it works!

Here's the PR.

[dmythro]

I hope it gets processed soon, I also planned to check it out and make a PR :)

[gorkem-bwl]

Related: #3380 — same root cause. The Uptime details page sends normalize=true, and server/src/utils/dataUtils.ts:74-88 rescales avgResponseTime into a fixed range (storing the real value as originalAvgResponseTime). client/src/Components/monitors/charts/HistogramDetails.tsx:71 then renders that normalized value as ${responseTime} ms, which looks like a percentage. The AVG tile uses raw monitorStats.avgResponseTime (correct), so the mismatch is purely in the histogram.