Question on diagnosing and debugging spicedb (especially in production). At the moment spicedb seems like a black box. You fire a check request and get a yes/no answer.
If we need to find out why spicedb arrived at a particular decision for a given check request, how can we go about it. I am looking for something that's programmatically consumable rather than have to turn on debugs and trawl through logs manually.
I haven't yet explored the inbuilt tracing support. Will that help here?