Tim Nolet

@DmitryFrolovTri thanks for the extensive write up. I think you are essentially describing SLO's, where there is an error budget for a time period. This is something I will keep...

@coderkind this is great feedback. 1. exposing the log data through the API is something we can do. Right now we store just an S3 filename in the DB which...

@andreas-svendby-adsk we have been actively discussing this internally, as we do the same thing: we monitor our staging and production with essentially the same checks. Now with our CLI https://github.com/checkly/checkly-cli...

@peter-dolkens we are tackling this in a larger Alerting V2 project later this year. I'm adding this ticket to the overarching one https://github.com/orgs/checkly/projects/4/views/4?pane=issue&itemId=21238722 On the specific topics you mentioned: the...

@aioue thanks for logging this! We've had this request a couple of times, so 100% noted. Our dashboard is already quite busy, so I'm always hesitant to add even more...

Hey @neskoncno thanks for reporting. Pinging Lead @jan-osch and PM @drakirnosslin

also mentioning https://github.com/checkly/public-roadmap/issues/87

Hey @chit786 thanks for contributing! We will ship new check types ASAP so this one goes on the list.

@chit786 now ETA on this that I would be comfortable giving you. But new check types (and even custom codable check types) is one of our main goals for 2023.

@bumi could you give me an example of what it is you would be monitoring on your current service / webapp? Do you use any other solution right now to...