Skip to main content

support BYOL, custom runtimes or add in 3rd party libraries

Feature RequestRuntimes

We have been using browser checks as intended and also not as intended. We are using browser scripts to monitor some of observability endpoints /push routes but sending json payloads. However one of the /push endpoints needs its payload to be protobuf encoded and compressed with snappy (see here more info on that). Protobufjs and snappy are both 3rd party libraries and are not part of any runtimes.

Is there a way to support users defining their own runtimes, bringing their own libraries or own runners (VMs, containers, etc), or maybe another type of check more catered to this instead of a browser check.

ty 🙏

Posted by Giancarlo ·
2 comments

Log in to comment and vote

Comments2

  • Tim Nolet

    •

    Dec 1, 2023

    Hey @Giancarlo this is indeed something of a dream for us too, but it's quite tricky to pull off given how we run things and the tradeoffs we have to deal with. I'm very interested in hearing the specifics of your use case as we can pretty easily add some libs to our runtime to enable protobuf via our multistep API checks (now in beta).

    https://feedback.checklyhq.com/changelog/6548d78dc9f7a1cf0013d75b

    • Giancarlo

      •

      Dec 1, 2023

      sure! We use grafana tooling for ingesting logs and metrics. We want checkly to verify if ingestion is working by sending POST requests with small data samples to be ingested by our grafana tooling. In this case Grafana Mimir ingests data that is protobuf encoded. One scenario also needs snappy to be used to compress the payload. Another scenario (which we will end up using) just needs a protobuf encoding. Let me know if i can answer anything else