ndimares

It makes sense. I think one of the challenges is the question of how much you need to store in order to be able to do this. Hanging onto every request/response object / parameters for an interaction with an API can be become expensive pretty quickly.

This becomes an issue when you start thinking about what is considered to be a bug. If you're just talking about error codes, then you're probably fine to store everything. But when you talk about unexplained (but not erroneous) behaviour from the API, how much you need to store to catch the bugs is an important consideration.

Do you view this as an improvement upon something like Hasura? If so, where do you think the improvement is coming from?

What do you think would be the ideal? A way for someone to replay an API request (without seeing it) in a dev environ?

I see a lot of value in being able to generate the schema based off of real time traffic, vs. static analysis or test cases. In my mind the traffic to the API is the real source of truth for the API.

You could try Akita Software: https://www.akitasoftware.com/ who exists in this space, but anecdotally devs I've spoken to who have tested that solution haven't loved it (find it hard/unintuitive to use). I assume a full investment (Data warehouse + datadog and alerting framework) would be overkill for your use case?

This problem is something I've spent some time thinking through/working on addressing, because it does feel like there should be something easy & low cost for devs to use, a mixpanel for API usage as it were. If you'd want to talk about it offline, drop me a message. Best of luck!