You already offer reports on caching opportunities, which is nice, but I'd really love to see a report that tells me how much better my users experience has been because of stellate, both for individual requests, and for the overall, in aggregate. You offer little pieces of this data, but having a comprehensive report would be really useful for selling internal teams on the tool and for helping understand the value of the tool.
Proxy non GraphQL requests to the backend as well.
In some cases the backend GraphQL API is also responsible for handling other requests. From an ease point of view, it would be great if Stellate would forward those requests as well.
Monetize my API
I'd like to monetize my GraphQL API and have Stellate take care of as much as possible in this process. That includes the metrics to know how much a user of my API used the API.
Support websocket subscriptions
We use Hasura subscriptions extensively, how can users still send us subscription requests after we move to GraphCDN?
Adapt time range via GUI
After being able to filter metrics by a custom time range (which is absolutely necessary and awesome) it would make sense to be able to set this time range via the GUI. Actually the GUI kind of suggests, that this is actually possible. When hovering over the timeline, there is this grey box showing details about this specific time frame. The only thing which is missing is a click which adapts the custom time range accordingly. Relates to: https://feedback.stellate.co/feature-requests/p/custom-time-range-selection-for-metrics
Disable introspection on CDN but not on source
I would like to prevent users of the CDN from using the introspection query but allow it on the source so that GraphCDN can fetch my schema.
Configure Timeouts on Stellate
As a user I want to timeout requests taking longer than X seconds, and configure alerts to let me know if requests are running into timeouts.
CORS Blocking in GraphCDN
Caching GraphQL at the Edge is Really Awesome, but it would be too costly to allow everyone to send a queries that might have Spamming. One Solution for these problem would be Rate Limiting, but Implementing CORS would be very cool. Also CORS don't prevent from Server Side Query Requests.