QStash Released

Metrics per Queue/Flow-Control/Url are requested time to time but not implemented since they are basically expensive.

Problem:

QStash messages may contain sensitive data in the body or headers. Users need a way to redact these fields so they are not visible in the dashboard or API responses, preventing accidental data leaks. This also enables safer use of QStash in multi-tenant setups where customer…

Right now, the flow control is only configured with the publish. This makes it hard for our users to change the config when needed from outside.

Add ability to pause and resume flow control keys.

This is to give much-lower latencies when sending a message via accepting the request from the closest region.

Currently it is hard for our users to understand what is going on with Flow-Control/Global Parallellism.

Remember last X publishes from the console so that it can be run again easily.

This is aimed for development purposes.

Add ability to list the flow-controls on the console together with their waitListSizes.

Make it searchable.

QStash requires a publicly available API to send messages to. During development when applications are not yet deployed, developers typically need to expose their local API by creating a public tunnel. While local tunneling works seamlessly, it requires code changes between…