Tim Nolet

@jan-osch @Antoine-C do we have this on the radar?

@MMore thanks for contributing. Let me explain why we don't have that right now. Any check that is run on longer frequencies, e.g. 60 minutes will report a somewhat distorted...

@slmoore We JUST released a beta of the new runtime! It includes `data-fns`. Here is the blurb we just posted on our [community Slack.](https://www.checklyhq.com/slack) --- Hey Folks, I’m excited to...

@geirarne thanks for the clear feedback! Extremely useful and I 100% understand the concern. Let me have a look if we can squeeze that in before we go GA with...

@IanWhitney thanks for contributing. This smells a lot like "bucket based" / "budget based" alerting or SLOs. The immediate question I would have is "p99 over how much time?" as...

@mbernasocchi thanks for reporting! Taking notice for the next iteration.

Hey @pshanoop thanks for reporting this. Solid write up. We are actively looking at some different flavours of running Checkly for more private workloads. 1. On premise runners. This means...

@case thanks for the contribution. Labeled, but not planned yet!

@kostantin-stambolov thanks for mentioning this.

@heipei we are looking at (way) more flexible alerting the coming quarters. I added this ticket to the overarching one. https://github.com/orgs/checkly/projects/4/views/4?pane=issue&itemId=21238722