Status pages need from/to dates/times

[gorkem-bwl]

When hovered on the status page, we need to add hours to the chart. Also optionally suggest ways to add 7d, 30d and 90d options.

[chrastlet]

Hi! Is this issue still available? I'd be happy to work on it.

[gorkem-bwl]

Hi! Is this issue still available? I'd be happy to work on it.

Sure. Please make a short research about how others are doing this and come up with a few suggestions we can discuss here.

[chrastlet]

Hey, sorry for the late reply . The past two weeks have been pretty busy, but I finally had some time to check out the project and got it up and running.

Since I’m new to Checkmate, I’m not quite sure what the “hours” on the public status page are supposed to represent. Could you clarify what exactly they refer to? Just want to make sure I understand the context before moving forward.

[gorkem-bwl]

Since I’m new to Checkmate, I’m not quite sure what the “hours” on the public status page are supposed to represent. Could you clarify what exactly they refer to? Just want to make sure I understand the context before moving forward.

Sure. Hours would represent the hours that correspond to each chart bar.

[chrastlet]

Thanks, that helps!

In that case, I’ll go ahead and divide the chart bars into clear time intervals like:

Date – HH:MM to HH:MM
(e.g., July 17, 14:00–15:00)

That way adding more days shouldn't be problem.
Let me know if there’s anything else I should consider while implementing this.

[gorkem-bwl]

@ajhollid any suggestions / comments here?

[ajhollid]

@chrastlet @gorkem-bwl any issues pertaining to how data is presented in the chart generally need to be addressed from the back end.

Data should be aggregated and grouped at the database level.

If we're just talking about adding labels to the chart, that can be handled on the front end.

If we need new groupings / aggregation that needs to be done on the back end

[chrastlet]

Hey,
I’ve implemented the first version, is this what you had in mind?

I noticed that both createdAt and expiry in the check object always have the exact same timestamp. Did I miss something, or is that how the backend currently handles it?
You mentioned that this structure is meant for future use cases, like displaying time spans across multiple days.

I could adjust the display so that HH:MM – HH:MM is only shown when the times differ. Otherwise, I’d just show HH:MM.

[gorkem-bwl]

Hey,
I’ve implemented the first version, is this what you had in mind?

I noticed that both createdAt and expiry in the check object always have the exact same timestamp. Did I miss something, or is that how the backend currently handles it?
You mentioned that this structure is meant for future use cases, like displaying time spans across multiple days.

I could adjust the display so that HH:MM – HH:MM is only shown when the times differ. Otherwise, I’d just show HH:MM.

When the times are the same we can show only one.

Can you retrieve ping durations as well?

[chrastlet]

Does this look good to you? Let me know if you have any suggestions for improvement!

[gorkem-bwl]

Does this look good to you? Let me know if you have any suggestions for improvement!

LGTM. Is the time taken from the timezone selection in Settings?

[gorkem-bwl]

@chrastlet checking back for this ;)

[chrastlet]

Sorry for the wait, i've been pretty busy the last few weeks.
I basically took the time values from the server response. I don't know if the api call takes the time settings in account or not